Systems and methods for utilizing mobile access points for multiple-path delay tolerant communication in a network of moving things, for example including a network of autonomous vehicles

ABSTRACT

Systems and methods for optimizing data communication in a network of moving things. As non-limiting examples, various aspects of this disclosure provide systems and methods for communicating delay tolerant information in a network of moving things, for example comprising any of a variety of types of vehicles (e.g., autonomous vehicles, vehicles controlled by local operators, vehicles controlled by remote operators, etc.).

CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE

The present application is a continuation of U.S. patent applicationSer. No. 15/633,201, filed on Jun. 26, 2017, and titled “Systems andMethods for Multiple-Path Delay Tolerant Communication in a Network ofMoving Things, For Example Including a Network of Autonomous Vehicles,”expected to issue as U.S. Pat. No. 9,967,815, which is a continuation ofU.S. patent application Ser. No. 15/353,966, filed on Nov. 17, 2016, andtitled “Systems and Methods for Delay Tolerant Networking in a Networkof Moving Things, For Example Including a Network of AutonomousVehicles,” now U.S. Pat. No. 9,693,297, which makes reference to, claimspriority to, and claims benefit from U.S. Provisional Application Ser.No. 62/257,421, filed on Nov. 19, 2015, and titled “Systems and Methodsfor Delay Tolerant Networking in a Network of Moving Things,” each ofwhich is hereby incorporated herein by reference in its entirety.

The present application is also related to U.S. Provisional ApplicationSer. No. 62/221,997, titled “Integrated Communication Network for aNetwork of Moving Things,” filed on Sep. 22, 2015; U.S. ProvisionalApplication Ser. No. 62/222,016, titled “Systems and Methods forSynchronizing a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,042, titled “Systems and Methodsfor Managing a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,066, titled “Systems and Methodsfor Monitoring a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,077, titled “Systems and Methodsfor Detecting and Classifying Anomalies in a Network of Moving Things,”filed on Sep. 22, 2015; U.S. Provisional Application Ser. No.62/222,098, titled “Systems and Methods for Managing Mobility in aNetwork of Moving Things,” filed on Sep. 22, 2015; U.S. ProvisionalApplication Ser. No. 62/222,121, titled “Systems and Methods forManaging Connectivity a Network of Moving Things,” filed on Sep. 22,2015; U.S. Provisional Application Ser. No. 62/222,135, titled “Systemsand Methods for Collecting Sensor Data in a Network of Moving Things,”filed on Sep. 22, 2015; U.S. Provisional Application Ser. No.62/222,145, titled “Systems and Methods for Interfacing with a Networkof Moving Things,” filed on Sep. 22, 2015; U.S. Provisional ApplicationSer. No. 62/222,150, titled “Systems and Methods for Interfacing with aUser of a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,168, titled “Systems and Methodsfor Data Storage and Processing for a Network of Moving Things,” filedon Sep. 22, 2015; U.S. Provisional Application Ser. No. 62/222,183,titled “Systems and Methods for Vehicle Traffic Management in a Networkof Moving Things,” filed on Sep. 22, 2015; U.S. Provisional ApplicationSer. No. 62/222,186, titled “Systems and Methods for EnvironmentalManagement in a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,190, titled “Systems and Methodsfor Port Management in a Network of Moving Things,” filed on Sep. 22,2015; U.S. Provisional Patent Application Ser. No. 62/222,192, titled“Communication Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/244,828, titled “UtilizingHistorical Data to Correct GPS Data in a Network of Moving Things,”filed on Oct. 22, 2015; U.S. Provisional Application Ser. No.62/244,930, titled “Using Anchors to Correct GPS Data in a Network ofMoving Things,” filed on Oct. 22, 2015; U.S. Provisional ApplicationSer. No. 62/246,368, titled “Systems and Methods for Inter-ApplicationCommunication in a Network of Moving Things,” filed on Oct. 26, 2015;U.S. Provisional Application Ser. No. 62/246,372, titled “Systems andMethods for Probing and Validating Communication in a Network of MovingThings,” filed on Oct. 26, 2015; U.S. Provisional Application Ser. No.62/250,544, titled “Adaptive Rate Control for Vehicular Networks,” filedon Nov. 4, 2015; U.S. Provisional Application Ser. No. 62/273,878,titled “Systems and Methods for Reconfiguring and Adapting Hardware in aNetwork of Moving Things,” filed on Dec. 31, 2015; U.S. ProvisionalApplication Ser. No. 62/253,249, titled “Systems and Methods forOptimizing Data Gathering in a Network of Moving Things,” filed on Nov.10, 2015; U.S. Provisional Application Ser. No. 62/257,421, titled“Systems and Methods for Delay Tolerant Networking in a Network ofMoving Things,” filed on Nov. 19, 2015; U.S. Provisional ApplicationSer. No. 62/265,267, titled “Systems and Methods for Improving Coverageand Throughput of Mobile Access Points in a Network of Moving Things,”filed on Dec. 9, 2015; U.S. Provisional Application Ser. No. 62/270,858,titled “Channel Coordination in a Network of Moving Things,” filed onDec. 22, 2015; U.S. Provisional Application Ser. No. 62/257,854, titled“Systems and Methods for Network Coded Mesh Networking in a Network ofMoving Things,” filed on Nov. 20, 2015; U.S. Provisional ApplicationSer. No. 62/260,749, titled “Systems and Methods for Improving FixedAccess Point Coverage in a Network of Moving Things,” filed on Nov. 30,2015; U.S. Provisional Application Ser. No. 62/273,715, titled “Systemsand Methods for Managing Mobility Controllers and Their NetworkInteractions in a Network of Moving Things,” filed on Dec. 31, 2015;U.S. Provisional Application Ser. No. 62/281,432, titled “Systems andMethods for Managing and Triggering Handovers of Mobile Access Points ina Network of Moving Things,” filed on Jan. 21, 2016; U.S. ProvisionalApplication Ser. No. 62/268,188, titled “Captive Portal-related Controland Management in a Network of Moving Things,” filed on Dec. 16, 2015;U.S. Provisional Application Ser. No. 62/270,678, titled “Systems andMethods to Extrapolate High-Value Data from a Network of Moving Things,”filed on Dec. 22, 2015; U.S. Provisional Application Ser. No.62/272,750, titled “Systems and Methods for Remote Software Update andDistribution in a Network of Moving Things,” filed on Dec. 30, 2015;U.S. Provisional Application Ser. No. 62/278,662, titled “Systems andMethods for Remote Configuration Update and Distribution in a Network ofMoving Things,” filed on Jan. 14, 2016; U.S. Provisional ApplicationSer. No. 62/286,243, titled “Systems and Methods for Adapting a Networkof Moving Things Based on User Feedback,” filed on Jan. 22, 2016; U.S.Provisional Application Ser. No. 62/278,764, titled “Systems and Methodsto Guarantee Data Integrity When Building Data Analytics in a Network ofMoving Things,” Jan. 14, 2016; U.S. Provisional Application Ser. No.62/286,515, titled “Systems and Methods for Self-Initialization andAutomated Bootstrapping of Mobile Access Points in a Network of MovingThings,” filed on Jan. 25, 2016; U.S. Provisional Application Ser. No.62/295,602, titled “Systems and Methods for Power Management in aNetwork of Moving Things,” filed on Feb. 16, 2016; and U.S. ProvisionalApplication Ser. No. 62/299,269, titled “Systems and Methods forAutomating and Easing the Installation and Setup of the InfrastructureSupporting a Network of Moving Things,” filed on Feb. 24, 2016; each ofwhich is hereby incorporated herein by reference in its entirety for allpurposes.

BACKGROUND

Current communication networks are unable to adequately supportcommunication environments involving moving networks. As a non-limitingexample, current communication networks are unable to adequately supporta network comprising a complex array of both moving and static nodes,some of which may be network access points (e.g., the Internet of movingthings) interacting with sensor systems. Limitations and disadvantagesof conventional methods and systems will become apparent to one of skillin the art, through comparison of such approaches with some aspects ofthe present methods and systems set forth in the remainder of thisdisclosure with reference to the drawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIG. 2 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIG. 3 shows a diagram of a metropolitan area network, in accordancewith various aspects of this disclosure.

FIG. 4 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIGS. 5A-5C show a plurality of network configurations illustrating theflexibility and/or and resiliency of a communication network, inaccordance with various aspects of this disclosure.

FIG. 6 shows a block diagram of an example communication network, inaccordance with various aspects of the present disclosure.

FIG. 7 shows a block diagram of an example communication network, inaccordance with various aspects of the present disclosure.

FIG. 8 shows a block diagram of a system and method at a node for delaytolerant networking, in accordance with various aspects of the presentdisclosure.

FIG. 9 shows a block diagram of a system and method in a mobile networkfor delay tolerant networking, in accordance with various aspects of thepresent disclosure.

FIG. 10 shows a block diagram of a system and method in a mobile networkfor delay tolerant networking, in accordance with various aspects of thepresent disclosure.

FIG. 11 shows a block diagram of a system and method at a node for delaytolerant networking, in accordance with various aspects of the presentdisclosure.

FIG. 12 shows a block diagram of a system and method in a mobile networkfor delay tolerant networking, in accordance with various aspects of thepresent disclosure.

FIG. 13 shows a block diagram of a method in a node for delay tolerantnetworking, in accordance with various aspects of the presentdisclosure.

FIG. 14 shows a block diagram of a method in a node for delay tolerantnetworking, in accordance with various aspects of the presentdisclosure.

FIG. 15 shows a block diagram of various components of an example mobilecommunication network, in accordance with various aspects of the presentdisclosure.

SUMMARY

Various aspects of this disclosure provide systems and methods foroptimizing data communication in a network of moving things. Asnon-limiting examples, various aspects of this disclosure providesystems and methods for communicating delay tolerant information in anetwork of moving things, for example comprising any of a variety oftypes of vehicles (e.g., autonomous vehicles, vehicles controlled bylocal operators, vehicles controlled by remote operators, etc.).

DETAILED DESCRIPTION OF VARIOUS ASPECTS OF THE DISCLOSURE

As utilized herein the terms “circuits” and “circuitry” refer tophysical electronic components (i.e., hardware) and any software and/orfirmware (“code”) that may configure the hardware, be executed by thehardware, and or otherwise be associated with the hardware. As usedherein, for example, a particular processor and memory (e.g., a volatileor non-volatile memory device, a general computer-readable medium, etc.)may comprise a first “circuit” when executing a first one or more linesof code and may comprise a second “circuit” when executing a second oneor more lines of code. Additionally, a circuit may comprise analogand/or digital circuitry. Such circuitry may, for example, operate onanalog and/or digital signals. It should be understood that a circuitmay be in a single device or chip, on a single motherboard, in a singlechassis, in a plurality of enclosures at a single geographical location,in a plurality of enclosures distributed over a plurality ofgeographical locations, etc. Similarly, the term “module” may, forexample, refer to a physical electronic components (i.e., hardware) andany software and/or firmware (“code”) that may configure the hardware,be executed by the hardware, and or otherwise be associated with thehardware.

As utilized herein, circuitry is “operable” to perform a functionwhenever the circuitry comprises the necessary hardware and code (if anyis necessary) to perform the function, regardless of whether performanceof the function is disabled, or not enabled (e.g., by auser-configurable setting, factory setting or trim, etc.).

As utilized herein, “and/or” means any one or more of the items in thelist joined by “and/or”. As an example, “x and/or y” means any elementof the three-element set {(x), (y), (x, y)}. That is, “x and/or y” means“one or both of x and y.” As another example, “x, y, and/or z” means anyelement of the seven-element set {(x), (y), (z), (x, y), (x, z), (y, z),(x, y, z)}. That is, “x, y, and/or x” means “one or more of x, y, andz.” As utilized herein, the terms “e.g.,” and “for example,”“exemplary,” and the like set off lists of one or more non-limitingexamples, instances, or illustrations.

The terminology used herein is for the purpose of describing particularexamples only and is not intended to be limiting of the disclosure. Asused herein, the singular forms are intended to include the plural formsas well, unless the context clearly indicates otherwise. It will befurther understood that the terms “comprises,” “includes,” “comprising,”“including,” “has,” “have,” “having,” and the like when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

It will be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms. These terms are only used to distinguish oneelement from another element. Thus, for example, a first element, afirst component or a first section discussed below could be termed asecond element, a second component or a second section without departingfrom the teachings of the present disclosure. Similarly, various spatialterms, such as “upper,” “lower,” “side,” and the like, may be used indistinguishing one element from another element in a relative manner. Itshould be understood, however, that components may be oriented indifferent manners, for example an electronic device may be turnedsideways so that its “top” surface is facing horizontally and its “side”surface is facing vertically, without departing from the teachings ofthe present disclosure.

With the proliferation of the mobile and/or static things (e.g.,devices, machines, people, etc.) and logistics for such things to becomeconnected to each other (e.g., in the contexts of smart logistics,transportation, environmental sensing, etc.), a platform that is forexample always-on, robust, scalable and secure that is capable ofproviding connectivity, services and Internet access to such things (orobjects), anywhere and anytime is desirable. Efficient power utilizationwithin the various components of such system is also desirable.

Accordingly, various aspects of the present disclosure provide afully-operable, always-on, responsive, robust, scalable, secureplatform/system/architecture to provide connectivity, services andInternet access to all mobile things and/or static things (e.g.,devices, machines, people, access points, end user devices, sensors,etc.) anywhere and anytime, while operating in an energy-efficientmanner.

Various aspects of the present disclosure provide a platform that isflexibly configurable and adaptable to the various requirements,features, and needs of different environments, where each environmentmay be characterized by a respective level of mobility and density ofmobile and/or static things, and the number and/or types of access tothose things. Characteristics of various environments may, for example,include high mobility of nodes (e.g., causing contacts or connections tobe volatile), high number of neighbors, high number of connected mobileusers, mobile access points, availability of multiple networks andtechnologies (e.g., sometimes within a same area), etc. For example, themode of operation of the platform may be flexibly adapted fromenvironment to environment, based on each environment's respectiverequirements and needs, which may be different from other environments.Additionally for example, the platform may be flexibly optimized (e.g.,at design/installation time and/or in real-time) for different purposes(e.g., to reduce the latency, increase throughput, reduce powerconsumption, load balance, increase reliability, make more robust withregard to failures or other disturbances, etc.), for example based onthe content, service or data that the platform provides or handleswithin a particular environment.

In accordance with various aspects of the present disclosure, manycontrol and management services (e.g., mobility, security, routing,etc.) are provided on top of the platform (e.g., directly, using controloverlays, using containers, etc.), such services being compatible withthe services currently deployed on top of the Internet or othercommunication network(s).

The communication network (or platform), in whole or in part, may forexample be operated in public and/or private modes of operation, forexample depending on the use case. The platform may, for example,operate in a public or private mode of operation, depending on theuse-case (e.g., public Internet access, municipal environment sensing,fleet operation, etc.).

Additionally for example, in an implementation in which various networkcomponents are mobile, the transportation and/or signal controlmechanisms may be adapted to serve the needs of the particularimplementation. Also for example, wireless transmission power and/orrate may be adapted (e.g., to mitigate interference, to reduce powerconsumption, to extend the life of network components, etc.

Various example implementations of a platform, in accordance withvarious aspects of the present disclosure, are capable of connectingdifferent subsystems, even when various other subsystems that maynormally be utilized are unavailable. For example, the platform maycomprise various built-in redundancies and fail-recovery mechanisms. Forexample, the platform may comprise a self-healing capability,self-configuration capability, self-adaptation capability, etc. Theprotocols and functions of the platform may, for example, be prepared tobe autonomously and smoothly configured and adapted to the requirementsand features of different environments characterized by different levelsof mobility and density of things (or objects), the number/types ofaccess to those things. For example, various aspects of the platform maygather context parameters that can influence any or all decisions. Suchparameters may, for example, be derived locally, gathered from aneighborhood, Fixed APs, the Cloud, etc. Various aspects of the platformmay also, for example, ask for historical information to feed any of thedecisions, where such information can be derived from historical data,from surveys, from simulators, etc. Various aspects of the platform mayadditionally, for example, probe or monitor decisions made throughoutthe network, for example to evaluate the network and/or the decisionsthemselves in real-time. Various aspects of the platform may further,for example, enforce the decisions in the network (e.g., afterevaluating the probing results). Various aspects of the platform may,for example, establish thresholds to avoid any decision that is to beconstantly or repeatedly performed without any significant advantage(e.g., technology change, certificate change, IP change, etc.). Variousaspects of the platform may also, for example, learn locally (e.g., withthe decisions performed) and dynamically update the decisions.

In addition to (or instead of) failure robustness, a platform mayutilize multiple connections (or pathways) that exist between distinctsub-systems or elements within the same sub-system, to increase therobustness and/or load-balancing of the system.

The following discussion will present examples of the functionalityperformed by various example subsystems of the communication network. Itshould be understood that the example functionality discussed hereinneed not be performed by the particular example subsystem or by a singlesubsystem. For example, the subsystems present herein may interact witheach other, and data or control services may be deployed either in acentralized way, or having their functionalities distributed among thedifferent subsystems, for example leveraging the cooperation between theelements of each subsystem.

Various aspects of the present disclosure provide a communicationnetwork (e.g., a city-wide vehicular network, a shipping port-sizedvehicular network, a campus-wide vehicular network, etc.) that utilizesvehicles (e.g., automobiles, buses, trucks, boats, forklifts,human-operated vehicles, autonomous and/or remote controlled vehicles,etc.) as Wi-Fi hotspots. Note that Wi-Fi is generally used throughoutthis discussion as an example, but the scope of various aspects of thisdisclosure is not limited thereto. For example, other wireless LANtechnologies, PAN technologies, MAN technologies, etc., may be utilized.Such utilization may, for example, provide cost-effective ways to gathersubstantial amounts of urban data, and provide for the efficientoffloading of traffic from congested cellular networks (or othernetworks). In controlled areas (e.g., ports, harbors, etc.) with manyvehicles, a communication network in accordance with various aspects ofthis disclosure may expand the wireless coverage of existing enterpriseWi-Fi networks, for example providing for real-time communication withvehicle drivers (e.g., human, computer-controlled, etc.) and othermobile employees without the need for SIM cards or cellular (or othernetwork) data plans.

Vehicles may have many advantageous characteristics that make themuseful as Wi-Fi (or general wireless) hotspots. For example, vehiclesgenerally have at least one battery, vehicles are generally denselyspread over the city at street level and/or they are able to establishmany contacts with each other in a controlled space, and vehicles cancommunicate with 10× the range of normal Wi-Fi in the 5.9 GHz frequencyband, reserved for intelligent transportation systems in the EU, theU.S., and elsewhere. Note that the scope of this disclosure is notlimited to such 5.9 GHz wireless communication. Further, vehicles areable to effectively expand their coverage area into a swath over aperiod of time, enabling a single vehicle access point to interact withsubstantially more data sources over the period of time.

In accordance with various aspects of the present disclosure, anaffordable multi-network on-board unit (OBU) is presented. Note that theOBU may also be referred to herein as a mobile access point, Mobile AP,MAP, etc. The OBU may, for example, comprise a plurality of networkinginterfaces (e.g., Wi-Fi, 802.11p, 4G, Bluetooth, UWB, etc.). The OBUmay, for example, be readily installed in or on private and/or publicvehicles (e.g., individual user vehicles, vehicles of private fleets,vehicles of public fleets, etc.). The OBU may, for example, be installedin transportation fleets, waste management fleets, law enforcementfleets, emergency services, road maintenance fleets, taxi fleets,aircraft fleets, etc. The OBU may, for example, be installed in or on avehicle or other structure with free mobility or relatively limitedmobility. The OBU may also, for example, be carried by a person orservice animal, mounted to a bicycle, mounted to a moving machine ingeneral, mounted to a container, etc.

The OBUs may, for example, operate to connect passing vehicles to thewired infrastructure of one or more network providers, telecomoperators, etc. In accordance with the architecture, hardware, andsoftware functionality discussed herein, vehicles and fleets can beconnected not just to the cellular networks (or other wide area ormetropolitan area networks, etc.) and existing Wi-Fi hotspots spreadover a city or a controlled space, but also to other vehicles (e.g.,utilizing multi-hop communications to a wired infrastructure, single ormulti-hop peer-to-peer vehicle communication, etc.). The vehicles and/orfleets may, for example, form an overall mesh of communication links,for example including the OBUs and also fixed Access Points (APs)connected to the wired infrastructure (e.g., a local infrastructure,etc.). Note that OBUs herein may also be referred to as “Mobile APs,”“mobile hotspots,” “MAPs,” etc. Also note that fixed access points mayalso be referred to herein as Road Side Units (RSUs), Fixed APs, FAPs,etc.

In an example implementation, the OBUs may communicate with the FixedAPs utilizing a relatively long-range protocol (e.g., 802.11p, etc.),and the Fixed APs may, in turn, be hard wired to the wiredinfrastructure (e.g., via cable, tethered optical link, etc.). Note thatFixed APs may also, or alternatively, be coupled to the infrastructurevia wireless link (e.g., 802.11p, etc.). Additionally, clients or userdevices may communicate with the OBUs using one or more relativelyshort-range protocols (e.g., Wi-Fi, Bluetooth, UWB, etc.). The OBUs, forexample having a longer effective wireless communication range thantypical Wi-Fi access points or other wireless LAN/PAN access points(e.g., at least for links such as those based on 802.11p, etc.), arecapable of substantially greater coverage areas than typical Wi-Fi orother wireless LAN/PAN access points, and thus fewer OBUs are necessaryto provide blanket coverage over a geographical area.

The OBU may, for example, comprise a robust vehicular networking module(e.g., a connection manager) which builds on long-range communicationprotocol capability (e.g., 802.11p, etc.). For example, in addition tocomprising 802.11p (or other long-range protocol) capability tocommunicate with Fixed APs, vehicles, and other nodes in the network,the OBU may comprise a network interface (e.g., 802.11a/b/g/n, 802.11ac,802.11af, any combination thereof, etc.) to provide wireless local areanetwork (WLAN) connectivity to end user devices, sensors, fixed Wi-Fiaccess points, etc. For example, the OBU may operate to providein-vehicle Wi-Fi Internet access to users in and/or around the vehicle(e.g., a bus, train car, taxi cab, public works vehicle, etc.). The OBUmay further comprise one or more wireless backbone communicationinterfaces (e.g., cellular network interfaces, etc.). Though in variousexample scenarios, a cellular network interface (or other wirelessbackbone communication interface) might not be the preferred interfacefor various reasons (e.g., cost, power, bandwidth, etc.), the cellularnetwork interface may be utilized to provide connectivity ingeographical areas that are not presently supported by a Fixed AP, maybe utilized to provide a fail-over communication link, may be utilizedfor emergency communications, may be utilized to subscribe to localinfrastructure access, etc. The cellular network interface may also, forexample, be utilized to allow the deployment of solutions that aredependent on the cellular network operators.

An OBU, in accordance with various aspects of the present disclosure,may for example comprise a smart connection manager that can select thebest available wireless link(s) (e.g., Wi-Fi, 802.11p, cellular, vehiclemesh, etc.) with which to access the Internet. The OBU may also, forexample, provide geo-location capabilities (e.g., GPS, etc.), motiondetection sensors to determine if the vehicle is in motion, and a powercontrol subsystem (e.g., to ensure that the OBU does not deplete thevehicle battery, etc.). The OBU may, for example, comprise any or all ofthe sensors (e.g., environmental sensors, etc.) discussed herein.

The OBU may also, for example, comprise a manager that managesmachine-to-machine data acquisition and transfer (e.g., in a real-timeor delay-tolerant fashion) to and from the cloud. For example, the OBUmay log and/or communicate information of the vehicles.

The OBU may, for example, comprise a connection and/or routing managerthat operates to perform routing of communications in avehicle-to-vehicle/vehicle-to-infrastructure multi-hop communication. Amobility manager (or controller, MC) may, for example, ensure thatcommunication sessions persist over one or more handoff(s) (alsoreferred to herein as a “handover” or “handovers”) (e.g., betweendifferent Mobile APs, Fixed APs, base stations, hot spots, etc.), amongdifferent technologies (e.g., 802.11p, cellular, Wi-Fi, satellite,etc.), among different MCs (e.g., in a fail-over scenario, loadredistribution scenario, etc.), across different interfaces (or ports),etc. Note that the MC may also be referred to herein as a Local MobilityAnchor (LMA), a Network Controller, etc. Note that the MC, or aplurality thereof, may for example be implemented as part of thebackbone, but may also, or alternatively, be implemented as part of anyof a variety of components or combinations thereof. For example, the MCmay be implemented in a Fixed AP (or distributed system thereof), aspart of an OBU (or a distributed system thereof), etc. Variousnon-limiting examples of system components and/or methods are providedin U.S. Provisional Application No. 62/222,098, filed Sep. 22, 2015, andtitled “Systems and Method for Managing Mobility in a Network of MovingThings,” the entire contents of which are hereby incorporated herein byreference. Note that in an example implementation including a pluralityof MCs, such MCs may be co-located and/or may be geographicallydistributed.

Various aspects of the present disclosure also provide a cloud-basedservice-oriented architecture that handles the real-time management,monitoring and reporting of the network and clients, the functionalitiesrequired for data storage, processing and management, the Wi-Fi clientauthentication and Captive Portal display, etc.

A communication network (or component thereof) in accordance withvarious aspects of the present disclosure may, for example, support awide range of smart city applications (or controlled scenarios, orconnected scenarios, etc.) and/or use-cases, as described herein.

For example, an example implementation may operate to turn each vehicle(e.g., both public and private taxis, buses, trucks, etc.) into a MobileAP (e.g., a mobile Wi-Fi hotspot), offering Internet access toemployees, passengers and mobile users travelling in the city, waitingin bus stops, sitting in parks, etc. Moreover, through an examplevehicular mesh network formed between vehicles and/or fleets ofvehicles, an implementation may be operable to offload cellular trafficthrough the mobile Wi-Fi hotspots and/or Fixed APs (e.g., 802.11p-basedAPs) spread over the city and connected to the wired infrastructure ofpublic or private telecom operators in strategic places, while ensuringthe widest possible coverage at the lowest possible cost.

An example implementation (e.g., of a communication network and/orcomponents thereof) may, for example, be operable as a massive urbanscanner that gathers large amounts of data (e.g., continuously)on-the-move, actionable or not, generated by a myriad of sourcesspanning from the in-vehicle sensors or On Board Diagnostic System port(e.g., OBD2, etc.), interface with an autonomous vehicle driving system,external Wi-Fi/Bluetooth-enabled sensing units spread over the city,devices of vehicles' drivers and passengers (e.g., informationcharacterizing such devices and/or passengers, etc.), positioning systemdevices (e.g., position information, velocity information, trajectoryinformation, travel history information, etc.), etc.

Depending on the use case, the OBU may for example process (or computer,transform, manipulate, aggregate, summarize, etc.) the data beforesending the data from the vehicle, for example providing the appropriategranularity (e.g., value resolution) and sampling rates (e.g., temporalresolution) for each individual application. For example, the OBU may,for example, process the data in any manner deemed advantageous by thesystem. The OBU may, for example, send the collected data (e.g., rawdata, preprocessed data, information of metrics calculated based on thecollected data, etc.) to the Cloud (e.g., to one or more networkedservers coupled to any portion of the network) in an efficient andreliable manner to improve the efficiency, environmental impact andsocial value of municipal city operations and transportation services.Various example use cases are described herein.

In an example scenario in which public buses are moving along cityroutes and/or taxis are performing their private transportationservices, the OBU is able to collect large quantities of real-time datafrom the positioning systems (e.g., GPS, etc.), from accelerometermodules, etc. The OBU may then, for example, communicate such data tothe Cloud, where the data may be processed, reported and viewed, forexample to support such public or private bus and/or taxi operations,for example supporting efficient remote monitoring and scheduling ofbuses and taxis, respectively.

In an example implementation, small cameras (or other sensors) may becoupled to small single-board computers (SBCs) that are placed above thedoors of public buses to allow capturing image sequences of peopleentering and leaving buses, and/or on stops along the bus routes inorder to estimate the number of people waiting for a bus. Such data maybe gathered by the OBU in order to be sent to the Cloud. With such data,public transportation systems may detect peaks; overcrowded buses,routes and stops; underutilized buses, routes and stops; etc., enablingaction to be taken in real-time (e.g., reducing bus periodicity todecrease fuel costs and CO₂ emissions where and when passenger flows aresmaller, etc.) as well as detecting systematic transportation problems.

An OBU may, for example, be operable to communicate with any of avariety of Wi-Fi-enabled sensor devices equipped with a heterogeneouscollection of environmental sensors. Such sensors may, for example,comprise noise sensors (microphones, etc.), gas sensors (e.g., sensingCO, NO₂, O₃, volatile organic compounds (or VOCs), CO₂, etc.), smokesensors, pollution sensors, meteorological sensors (e.g., sensingtemperature, humidity, luminosity, particles, solar radiation, windspeed (e.g., anemometer), wind direction, rain (e.g., a pluviometer),optical scanners, biometric scanners, cameras, microphones, etc.). Suchsensors may also comprise sensors associated with users (e.g., vehicleoperators or passengers, passersby, etc.) and/or their personal devices(e.g., smart phones or watches, biometrics sensors, wearable sensors,implanted sensors, etc.). Such sensors may, for example, comprisesensors and/or systems associated with on-board diagnostic (OBD) unitsfor vehicles, autonomous vehicle driving systems, etc. Such sensors may,for example, comprise positioning sensors (e.g., GPS sensors, Galileosensors, GLONASS sensors, etc.). Note that such positioning sensors maybe part of a vehicle's operational system (e.g., a localhuman-controlled vehicle, an autonomous vehicle, a remotehuman-controlled vehicle, etc.) Such sensors may, for example, comprisecontainer sensors (e.g., garbage can sensors, shipping containersensors, container environmental sensors, container tracking sensors,etc.).

Once a vehicle enters the vicinity of such a sensor device, a wirelesslink may be established, so that the vehicle (or OBU thereof) cancollect sensor data from the sensor device and upload the collected datato a database in the Cloud. The appropriate action can then be taken. Inan example waste management implementation, several waste management (orcollection) trucks may be equipped with OBUs that are able toperiodically communicate with sensors installed on containers in orderto gather information about waste level, time passed since lastcollection, etc. Such information may then sent to the Cloud (e.g., to awaste management application coupled to the Internet, etc.) through thevehicular mesh network, in order to improve the scheduling and/orrouting of waste management trucks. Note that various sensors may alwaysbe in range of the Mobile AP (e.g., vehicle-mounted sensors). Note thatthe sensor may also (or alternatively) be mobile (e.g., a sensor mountedto another vehicle passing by a Mobile AP or Fixed AP, a drone-mountedsensor, a pedestrian-mounted sensor, etc.).

In an example implementation, for example in a controlled space (e.g., aport, harbor, airport, factory, plantation, mine, etc.) with manyvehicles, machines and employees, a communication network in accordancewith various aspects of the present disclosure may expand the wirelesscoverage of enterprise and/or local Wi-Fi networks, for example withoutresorting to a Telco-dependent solution based on SIM cards or cellularfees. In such an example scenario, apart from avoiding expensivecellular data plans, limited data rate and poor cellular coverage insome places, a communication network in accordance with various aspectsof the present disclosure is also able to collect and/or communicatelarge amounts of data, in a reliable and real-time manner, where suchdata may be used to optimize harbor logistics, transportationoperations, etc.

For example in a port and/or harbor implementation, by gatheringreal-time information on the position, speed, fuel consumption and CO₂emissions of the vehicles, the communication network allows a portoperator to improve the coordination of the ship loading processes andincrease the throughput of the harbor. Also for example, thecommunication network enables remote monitoring of drivers' behaviors,behaviors of autonomous vehicles and/or control systems thereof, trucks'positions and engines' status, and then be able to provide real-timenotifications to drivers (e.g., to turn on/off the engine, follow theright route inside the harbor, take a break, etc.), for example humandrivers and/or automated vehicle driving systems, thus reducing thenumber and duration of the harbor services and trips. Harbor authoritiesmay, for example, quickly detect malfunctioning trucks and abnormaltrucks' circulation, thus avoiding accidents in order to increase harborefficiency, security, and safety. Additionally, the vehicles can alsoconnect to Wi-Fi access points from harbor local operators, and provideWi-Fi Internet access to vehicles' occupants and surrounding harboremployees, for example allowing pilots to save time by filing reportsvia the Internet while still on the water.

FIG. 1 shows a block diagram of a communication network 100, inaccordance with various aspects of this disclosure. Any or all of thefunctionality discussed herein may be performed by any or all of theexample components of the example network 100. Also, the example network100 may, for example, share any or all characteristics with the otherexample methods, networks and/or network components 200, 300, 400,500-570, 600, 700, 800, 900, 1000, 1100, 1200, 1300, 1400, and 1500,discussed herein.

The example network 100, for example, comprises a Cloud that may, forexample comprise any of a variety of network level components. The Cloudmay, for example, comprise any of a variety of server systems executingapplications that monitor and/or control components of the network 100.Such applications may also, for example, manage the collection ofinformation from any of a large array of networked information sources,many examples of which are discussed herein. The Cloud (or a portionthereof) may also be referred to, at times, as an API. For example,Cloud (or a portion thereof) may provide one or more applicationprogramming interfaces (APIs) which other devices may use forcommunicating/interacting with the Cloud.

An example component of the Cloud may, for example, manageinteroperability with various multi-cloud systems and architectures.Another example component (e.g., a Cloud service component) may, forexample, provide various cloud services (e.g., captive portal services,authentication, authorization, and accounting (AAA) services, APIGateway services, etc.). An additional example component (e.g., aDevCenter component) may, for example, provide network monitoring and/ormanagement functionality, manage the implementation of software updates,etc. A further example component of the Cloud may manage data storage,data analytics, data access, etc. A still further example component ofthe Cloud may include any of a variety of third-partly applications andservices.

The Cloud may, for example, be coupled to the Backbone/CoreInfrastructure of the example network 100 via the Internet (e.g.,utilizing one or more Internet Service Providers). Though the Internetis provided by example, it should be understood that scope of thepresent disclosure is not limited thereto.

The Backbone/Core may, for example, comprise any one or more differentcommunication infrastructure components. For example, one or moreproviders may provide backbone networks or various components thereof.As shown in the example network 100 illustrated in FIG. 1, a Backboneprovider may provide wireline access (e.g., PSTN, fiber, cable, etc.).Also for example, a Backbone provider may provide wireless access (e.g.,Microwave, LTE/Cellular, 5G/TV Spectrum, etc.).

The Backbone/Core may also, for example, comprise one or more LocalInfrastructure Providers. The Backbone/Core may also, for example,comprise a private infrastructure (e.g., run by the network 100implementer, owner, etc.). The Backbone/Core may, for example, provideany of a variety of Backbone Services (e.g., AAA, Mobility, Monitoring,Addressing, Routing, Content services, Gateway Control services, etc.).

The Backbone/Core Infrastructure may comprise any of a variety ofcharacteristics, non-limiting examples of which are provided herein. Forexample, the Backbone/Core may be compatible with different wireless orwired technologies for backbone access. The Backbone/Core may also beadaptable to handle public (e.g., municipal, city, campus, etc.) and/orprivate (e.g., ports, campus, etc.) network infrastructures owned bydifferent local providers, and/or owned by the network implementer orstakeholder. The Backbone/Core may, for example, comprise and/orinterface with different Authentication, Authorization, and Accounting(AAA) mechanisms.

The Backbone/Core Infrastructure may, for example, support differentmodes of operation (e.g., L2 in port implementations, L3 in on-landpublic transportation implementations, utilizing any one or more of aplurality of different layers of digital IP networking, any combinationsthereof, equivalents thereof, etc.) or addressing pools. TheBackbone/Core may also for example, be agnostic to the Cloud provider(s)and/or Internet Service Provider(s). Additionally for example, theBackbone/Core may be agnostic to requests coming from any or allsubsystems of the network 100 (e.g., Mobile APs or OBUs (On BoardUnits), Fixed APs or RSUs (Road Side Units), MCs (Mobility Controllers)or LMAs (Local Mobility Anchors) or Network Controllers, etc.) and/orthird-party systems.

The Backbone/Core Infrastructure may, for example, comprise the abilityto utilize and/or interface with different data storage/processingsystems (e.g., MongoDB, MySql, Redis, etc.). The Backbone/CoreInfrastructure may further, for example, provide different levels ofsimultaneous access to the infrastructure, services, data, etc.

The example network 100 may also, for example, comprise a Fixed HotspotAccess Network. Various example characteristics of such a Fixed HotspotAccess Network 200 are shown at FIG. 2. The example network 200 may, forexample, share any or all characteristics with the other examplemethods, networks and/or network components 100, 300, 400, 500-570, 600,700, 800, 900, 1000, 1100, 1200, 1300, 1400, and 1500, discussed herein.

In the example network 200, the Fixed APs (e.g., the proprietary APs,the public third party APs, the private third party APs, etc.) may bedirectly connected to the local infrastructure provider and/or to thewireline/wireless backbone. Also for example, the example network 200may comprise a mesh between the various APs via wireless technologies.Note, however, that various wired technologies may also be utilizeddepending on the implementation. As shown, different fixed hotspotaccess networks can be connected to a same backbone provider, but mayalso be connected to different respective backbone providers. In anexample implementation utilizing wireless technology for backboneaccess, such an implementation may be relatively fault tolerant. Forexample, a Fixed AP may utilize wireless communications to the backbonenetwork (e.g., cellular, 3G, LTE, other wide or metropolitan areanetworks, etc.) if the backhaul infrastructure is down. Also forexample, such an implementation may provide for relatively easyinstallation (e.g., a Fixed AP with no cable power source that can beplaced virtually anywhere).

In the example network 200, the same Fixed AP can simultaneously provideaccess to multiple Fixed APs, Mobile APs (e.g., vehicle OBUs, etc.),devices, user devices, sensors, things, etc. For example, a plurality ofmobile hotspot access networks (e.g., OBU-based networks, etc.) mayutilize the same Fixed AP. Also for example, the same Fixed AP canprovide a plurality of simultaneous accesses to another single unit(e.g., another Fixed AP, Mobile AP, device, etc.), for example utilizingdifferent channels, different radios, etc.).

Note that a plurality of Fixed APs may be utilized forfault-tolerance/fail-recovery purposes. In an example implementation, aFixed AP and its fail-over AP may both be normally operational (e.g., ina same switch). Also for example, one or more Fixed APs may be placed inthe network at various locations in an inactive or monitoring mode, andready to become operational when needed (e.g., in response to a fault,in response to an emergency services need, in response to a data surge,etc.).

Referring back to FIG. 1, the example Fixed Hotspot Access Network isshown with a wireless communication link to a backbone provider (e.g.,to one or more Backbone Providers and/or Local InfrastructureProviders), to a Mobile Hotspot Access Network, to one or more End UserDevices, and to the Environment. Also, the example Fixed Hotspot AccessNetwork is shown with a wired communication link to one or more BackboneProviders, to the Mobile Hotspot Access Network, to one or more End UserDevices, and to the Environment. The Environment may comprise any of avariety of devices (e.g., in-vehicle networks, devices, and sensors;autonomous vehicle networks, devices, and sensors; maritime (orwatercraft) and port networks, devices, and sensors; generalcontrolled-space networks, devices, and sensors; residential networks,devices, and sensors; disaster recovery & emergency networks, devices,and sensors; military and aircraft networks, devices, and sensors; smartcity networks, devices, and sensors; event (or venue) networks, devices,and sensors; underwater and underground networks, devices, and sensors;agricultural networks, devices, and sensors; tunnel (auto, subway,train, etc.) networks, devices, and sensors; parking networks, devices,and sensors; security and surveillance networks, devices, and sensors;shipping equipment and container networks, devices, and sensors;environmental control or monitoring networks, devices, and sensors;municipal networks, devices, and sensors; waste management networks,devices, and sensors, road maintenance networks, devices, and sensors,traffic management networks, devices, and sensors; advertising networks,devices and sensors; etc.).

The example network 100 of FIG. 1 also comprises a Mobile Hotspot AccessNetwork. Various example characteristics of such a Mobile Hotspot AccessNetwork 300 are shown at FIG. 3. Note that various fixed networkcomponents (e.g., Fixed APs) are also illustrated. The example network300 may, for example, share any or all characteristics with the otherexample methods, networks and/or network components 100, 200, 400,500-570, 600, 700, 800, 900, 1000, 1100, 1200, 1300, 1400, and 1500,discussed herein.

The example network 300 comprises a wide variety of Mobile APs (orhotspots) that provide access to user devices, provide for sensor datacollection, provide multi-hop connectivity to other Mobile APs, etc. Forexample, the example network 300 comprises vehicles from differentfleets (e.g., aerial, terrestrial, underground, (under)water, etc.). Forexample, the example network 300 comprises one or more massdistribution/transportation fleets, one or more mass passengertransportation fleets, private/public shared-user fleets, privatevehicles, urban and municipal fleets, maintenance fleets, drones,watercraft (e.g., boats, ships, speedboats, tugboats, barges, etc.),emergency fleets (e.g., police, ambulance, firefighter, etc.), etc.

The example network 300, for example, shows vehicles from differentfleets directly connected and/or mesh connected, for example using sameor different communication technologies. The example network 300 alsoshows fleets simultaneously connected to different Fixed APs, which mayor may not belong to different respective local infrastructureproviders. As a fault-tolerance mechanism, the example network 300 mayfor example comprise the utilization of long-range wirelesscommunication network (e.g., cellular, 3G, 4G, LTE, etc.) in vehicles ifthe local network infrastructure is down or otherwise unavailable. Asame vehicle (e.g., Mobile AP or OBU) can simultaneously provide accessto multiple vehicles, devices, things, etc., for example using a samecommunication technology (e.g., shared channels and/or differentrespective channels thereof) and/or using a different respectivecommunication technology for each. Also for example, a same vehicle canprovide multiple accesses to another vehicle, device, thing, etc., forexample using a same communication technology (e.g., shared channelsand/or different respective channels thereof, and/or using a differentcommunication technology).

Additionally, multiple network elements may be connected together toprovide for fault-tolerance or fail recovery, increased throughput, orto achieve any or a variety of a client's networking needs, many ofexamples of which are provided herein. For example, two Mobile APs (orOBUs) may be installed in a same vehicle, etc.

Referring back to FIG. 1, the example Mobile Hotspot Access Network isshown with a wireless communication link to a backbone provider (e.g.,to one or more Backbone Providers and/or Local InfrastructureProviders), to a Fixed Hotspot Access Network, to one or more End UserDevice, and to the Environment (e.g., to any one of more of the sensorsor systems discussed herein, any other device or machine, etc.). Thoughthe Mobile Hotspot Access Network is not shown having a wired link tothe various other components, there may (at least at times) be such awired link, at least temporarily.

The example network 100 of FIG. 1 also comprises a set of End-UserDevices. Various example end user devices are shown at FIG. 4. Note thatvarious other network components (e.g., Fixed Hotspot Access Networks,Mobile Hotspot Access Network(s), the Backbone/Core, etc.) are alsoillustrated. The example network 400 may, for example, share any or allcharacteristics with the other example methods, networks and/or networkcomponents 100, 200, 300, 500-570, 600, 700, 800, 900, 1000, 1100, 1200,1300, 1400, and 1500, discussed herein.

The example network 400 shows various mobile networked devices. Suchnetwork devices may comprise end-user devices (e.g., smartphones,tablets, smartwatches, laptop computers, webcams, personal gamingdevices, personal navigation devices, personal media devices, personalcameras, health-monitoring devices, personal location devices,monitoring panels, printers, etc.). Such networked devices may alsocomprise any of a variety of devices operating in the generalenvironment, where such devices might not for example be associated witha particular user (e.g. any or all of the sensor devices discussedherein, vehicle sensors, municipal sensors, fleet sensors road sensors,environmental sensors, security sensors, traffic sensors, waste sensors,meteorological sensors, any of a variety of different types of municipalor enterprise equipment, etc.). Any of such networked devices can beflexibly connected to distinct backbone, fixed hotspot access networks,mobile hotspot access networks, etc., using the same or differentwired/wireless technologies.

A mobile device may, for example, operate as an AP to providesimultaneous access to multiple devices/things, which may then form adhoc networks, interconnecting devices ultimately connected to distinctbackbone networks, fixed hotspot, and/or mobile hotspot access networks.Devices (e.g., any or all of the devices or network nodes discussedherein) may, for example, have redundant technologies to access distinctbackbone, fixed hotspot, and/or mobile hotspot access networks, forexample for fault-tolerance and/or load-balancing purposes (e.g.,utilizing multiple SIM cards, etc.). A device may also, for example,simultaneously access distinct backbone, fixed hotspot access networks,and/or mobile hotspot access networks, belonging to the same provider orto different respective providers. Additionally for example, a devicecan provide multiple accesses to another device/thing (e.g., viadifferent channels, radios, etc.).

Referring back to FIG. 1, the example End-User Devices are shown with awireless communication link to a backbone provider (e.g., to one or moreBackbone Providers and/or Local Infrastructure Providers), to a FixedHotspot Access Network, to a Mobile Hotspot Access Network, and to theEnvironment. Also for example, the example End-User Devices are shownwith a wired communication link to a backbone provider, to a FixedHotspot Access Network, to a Mobile Hotspot Access Network, and to theEnvironment.

The example network 100 illustrated in FIG. 1 has a flexiblearchitecture that is adaptable at implementation time (e.g., fordifferent use cases) and/or adaptable in real-time, for example asnetwork components enter and leave service. FIGS. 5A-5C illustrate suchflexibility by providing example modes (or configurations). The examplenetworks 500-570 may, for example, share any or all characteristics withthe other example methods, networks and/or network components 100, 200,300, 400, 600, 700, 800, 900, 1000, 1100, 1200, 1300, 1400, and 1500,discussed herein. For example and without limitation, any or all of thecommunication links (e.g., wired links, wireless links, etc.) shown inthe example networks 500-570 are generally analogous to similarlypositioned communication links shown in the example network 100 of FIG.1.

For example, various aspects of this disclosure provide communicationnetwork architectures, systems, and methods for supporting a dynamicallyconfigurable communication network comprising a complex array of bothstatic and moving communication nodes (e.g., the Internet of movingthings). For example, a communication network implemented in accordancewith various aspects of the present disclosure may operate in one of aplurality of modalities comprising various fixed nodes, mobile nodes,and/or a combination thereof, which are selectable to yield any of avariety of system goals (e.g., increased throughput, reduced latency andpacket loss, increased availability and robustness of the system, extraredundancy, increased responsiveness, increased security in thetransmission of data and/or control packets, reduced number ofconfiguration changes by incorporating smart thresholds (e.g., change oftechnology, change of certificate, change of IP, etc.), providingconnectivity in dead zones or zones with difficult access, reducing thecosts for maintenance and accessing the equipment forupdating/upgrading, etc.). At least some of such modalities may, forexample, be entirely comprised of fixed-position nodes, at leasttemporarily if not permanently.

For illustrative simplicity, many of the example aspects shown in theexample system or network 100 of FIG. 1 (and other Figures herein) areomitted from FIGS. 5A-5C, but may be present. For example, the Cloud,Internet, and ISP aspects shown in FIG. 1 and in other Figures are notexplicitly shown in FIGS. 5A-5C, but may be present in any of theexample configurations (e.g., as part of the backbone provider networkor coupled thereto, as part of the local infrastructure provider networkor coupled thereto, etc.).

For example, the first example mode 500 is presented as a normalexecution mode, for example a mode (or configuration) in which all ofthe components discussed herein are present. For example, thecommunication system in the first example mode 500 comprises a backboneprovider network, a local infrastructure provider network, a fixedhotspot access network, a mobile hotspot access network, end-userdevices, and environment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the first example mode 500 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via a wired link. Note that such a wiredcoupling may be temporary. Also note that in various exampleconfigurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5A, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the first example mode 500 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links. Also note that in various example configurations,the backbone provider network may also be communicatively coupled to thelocal infrastructure provider network via one or more wireless (ornon-tethered) links.

Though not shown in the first example mode 500 (or any of the examplemodes of FIGS. 5A-5C), one or more servers may be communicativelycoupled to the backbone provider network and/or the local infrastructurenetwork. FIG. 1 provides an example of cloud servers beingcommunicatively coupled to the backbone provider network via theInternet.

As additionally shown in FIG. 5A, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the first example mode 500(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), fixed hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wired links. Note that such a wired coupling may be temporary. Alsonote that in various example configurations, the local infrastructureprovider network may also, at least temporarily, be communicativelycoupled to the mobile hotspot access network (or any component thereof)via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the first example mode 500 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the fixed hotspot access network (or any componentthereof), the mobile hotspot access network (or any component thereof),the end-user devices, and/or environment devices via one or morewireless links. Note that the communication link shown in the firstexample mode 500 of FIG. 5A between the local infrastructure providernetwork and the fixed hotspot access network may be wired and/orwireless.

The fixed hotspot access network is also shown in the first example mode500 to be communicatively coupled to the mobile hotspot access network,the end-user devices, and/or environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein. Additionally, the mobile hotspot access network is further shownin the first example mode 500 to be communicatively coupled to theend-user devices and/or environment devices via one or more wirelesslinks. Many examples of such wireless coupling are provided herein.Further, the end-user devices are also shown in the first example mode500 to be communicatively coupled to the environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Note that in various example implementations any ofsuch wireless links may instead (or in addition) comprise a wired (ortethered) link.

In the first example mode 500 (e.g., the normal mode), information (ordata) may be communicated between an end-user device and a server (e.g.,a computer system) via the mobile hotspot access network, the fixedhotspot access network, the local infrastructure provider network,and/or the backbone provider network. As will be seen in the variousexample modes presented herein, such communication may flexibly occurbetween an end-user device and a server via any of a variety ofdifferent communication pathways, for example depending on theavailability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the fixed hotspot access network, thelocal infrastructure provider network, and/or the backbone providernetwork (e.g., skipping the mobile hotspot access network). Also forexample, information communicated between an end user device and aserver may be communicated via the backbone provider network (e.g.,skipping the mobile hotspot access network, fixed hotspot accessnetwork, and/or local infrastructure provider network).

Similarly, in the first example mode 500 (e.g., the normal mode),information (or data) may be communicated between an environment deviceand a server via the mobile hotspot access network, the fixed hotspotaccess network, the local infrastructure provider network, and/or thebackbone provider network. Also for example, an environment device maycommunicate with or through an end-user device (e.g., instead of or inaddition to the mobile hotspot access network). As will be seen in thevarious example modes presented herein, such communication may flexiblyoccur between an environment device and a server (e.g., communicativelycoupled to the local infrastructure provider network and/or backboneprovider network) via any of a variety of different communicationpathways, for example depending on the availability of a network,depending on bandwidth utilization goals, depending on communicationpriority, depending on communication time (or latency) and/orreliability constraints, depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the fixed hotspot access network, thelocal infrastructure provider network, and/or the backbone providernetwork (e.g., skipping the mobile hotspot access network). Also forexample, information communicated between an environment device and aserver may be communicated via the backbone provider network (e.g.,skipping the mobile hotspot access network, fixed hotspot accessnetwork, and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the mobile hotspot access network and/or fixed hotspotaccess network).

As discussed herein, the example networks presented herein areadaptively configurable to operate in any of a variety of differentmodes (or configurations). Such adaptive configuration may occur atinitial installation and/or during subsequent controlled networkevolution (e.g., adding or removing any or all of the network componentsdiscussed herein, expanding or removing network capacity, adding orremoving coverage areas, adding or removing services, etc.). Suchadaptive configuration may also occur in real-time, for example inresponse to real-time changes in network conditions (e.g., networks orcomponents thereof being available or not based on vehicle oruser-device movement, network or component failure, network or componentreplacement or augmentation activity, network overloading, etc.). Thefollowing example modes are presented to illustrate characteristics ofvarious modes in which a communication system may operate in accordancewith various aspects of the present disclosure. The following examplemodes will generally be discussed in relation to the first example mode500 (e.g., the normal execution mode). Note that such example modes aremerely illustrative and not limiting.

The second example mode (or configuration) 510 (e.g., a no backboneavailable mode) may, for example, share any or all characteristics withthe first example mode 500, albeit without the backbone provider networkand communication links therewith. For example, the communication systemin the second example mode 510 comprises a local infrastructure providernetwork, a fixed hotspot access network, a mobile hotspot accessnetwork, end-user devices, and environment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the localinfrastructure provider network may be communicatively coupled to any orall of the other elements present in the second example mode 510 (orconfiguration) via one or more wired (or tethered) links. For example,the local infrastructure provider network may be communicatively coupledto the fixed hotspot access network (or any component thereof), theend-user devices, and/or environment devices via one or more wiredlinks. Note that such a wired coupling may be temporary. Also note thatin various example configurations, the local infrastructure providernetwork may also, at least temporarily, be communicatively coupled tothe mobile hotspot access network (or any component thereof) via one ormore wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the second example mode 510 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links. Note that the communication link(s) shown in thesecond example mode 510 of FIG. 5A between the local infrastructureprovider network and the fixed hotspot access network may be wiredand/or wireless.

The fixed hotspot access network is also shown in the second examplemode 510 to be communicatively coupled to the mobile hotspot accessnetwork, the end-user devices, and/or environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Additionally, the mobile hotspot access network isfurther shown in the second example mode 510 to be communicativelycoupled to the end-user devices and/or environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Further, the end-user devices are also shown in thesecond example mode 510 to be communicatively coupled to the environmentdevices via one or more wireless links. Many examples of such wirelesscoupling are provided herein. Note that in various exampleimplementations any of such wireless links may instead (or in addition)comprise a wired (or tethered) link.

In the second example mode 510 (e.g., the no backbone available mode),information (or data) may be communicated between an end-user device anda server (e.g., a computer, etc.) via the mobile hotspot access network,the fixed hotspot access network, and/or the local infrastructureprovider network. As will be seen in the various example modes presentedherein, such communication may flexibly occur between an end-user deviceand a server via any of a variety of different communication pathways,for example depending on the availability of a network, depending onbandwidth utilization goals, depending on communication priority,depending on communication time (or latency) and/or reliabilityconstraints, depending on cost, etc. For example, informationcommunicated between an end user device and a server may be communicatedvia the fixed hotspot access network and/or the local infrastructureprovider network (e.g., skipping the mobile hotspot access network).Also for example, information communicated between an end user deviceand a server may be communicated via the local infrastructure providernetwork (e.g., skipping the mobile hotspot access network and/or fixedhotspot access network).

Similarly, in the second example mode 510 (e.g., the no backboneavailable mode), information (or data) may be communicated between anenvironment device and a server via the mobile hotspot access network,the fixed hotspot access network, and/or the local infrastructureprovider network. Also for example, an environment device maycommunicate with or through an end-user device (e.g., instead of or inaddition to the mobile hotspot access network). As will be seen in thevarious example modes presented herein, such communication may flexiblyoccur between an environment device and a server (e.g., communicativelycoupled to the local infrastructure provider network) via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the fixed hotspot access network and/orthe local infrastructure provider network (e.g., skipping the mobilehotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thelocal infrastructure provider network (e.g., skipping the mobile hotspotaccess network and/or fixed hotspot access network).

The second example mode 510 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. Forexample, due to security and/or privacy goals, the second example mode510 may be utilized so that communication access to the public Cloudsystems, the Internet in general, etc., is not allowed. For example, allnetwork control and management functions may be within the localinfrastructure provider network (e.g., wired local network, etc.) and/orthe fixed access point network.

In an example implementation, the communication system might be totallyowned, operated and/or controlled by a local port authority. No extraexpenses associated with cellular connections need be spent. Forexample, cellular connection capability (e.g., in Mobile APs, Fixed APs,end user devices, environment devices, etc.) need not be provided. Notealso that the second example mode 510 may be utilized in a scenario inwhich the backbone provider network is normally available but iscurrently unavailable (e.g., due to server failure, due to communicationlink failure, due to power outage, due to a temporary denial of service,etc.).

The third example mode (or configuration) 520 (e.g., a no localinfrastructure and fixed hotspots available mode) may, for example,share any or all characteristics with the first example mode 500, albeitwithout the local infrastructure provider network, the fixed hotspotaccess network, and communication links therewith. For example, thecommunication system in the third example mode 520 comprises a backboneprovider network, a mobile hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the third example mode 520 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the end-user devicesand/or environment devices via one or more wired links. Note that such awired coupling may be temporary. Also note that in various exampleconfigurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5A, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the third example mode 520 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links.

The mobile hotspot access network is further shown in the third examplemode 520 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the third example mode 520 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein. Note that in various example implementations any of suchwireless links may instead (or in addition) comprise a wired (ortethered) link.

In the third example mode 520 (e.g., the no local infrastructure andfixed hotspots available mode), information (or data) may becommunicated between an end-user device and a server (e.g., a computer,etc.) via the mobile hotspot access network and/or the backbone providernetwork. As will be seen in the various example modes presented herein,such communication may flexibly occur between an end-user device and aserver via any of a variety of different communication pathways, forexample depending on the availability of a network, depending onbandwidth utilization goals, depending on communication priority,depending on communication time (or latency) and/or reliabilityconstraints, depending on cost, etc. For example, informationcommunicated between an end user device and a server may be communicatedvia the backbone provider network (e.g., skipping the mobile hotspotaccess network).

Similarly, in the third example mode 520 (e.g., the no localinfrastructure and fixed hotspots available mode), information (or data)may be communicated between an environment device and a server via themobile hotspot access network and/or the backbone provider network. Alsofor example, an environment device may communicate with or through anend-user device (e.g., instead of or in addition to the mobile hotspotaccess network). As will be seen in the various example modes presentedherein, such communication may flexibly occur between an environmentdevice and a server (e.g., communicatively coupled to the backboneprovider network) via any of a variety of different communicationpathways, for example depending on the availability of a network,depending on bandwidth utilization goals, depending on communicationpriority, depending on communication time (or latency) and/orreliability constraints, depending on cost, etc. For example,information communicated between an environment device and a server maybe communicated via the backbone provider network (e.g., skipping themobile hotspot access network).

In the third example mode 520, all control/management functions may forexample be implemented within the Cloud. For example, since the mobilehotspot access network does not have a communication link via a fixedhotspot access network, the Mobile APs may utilize a direct connection(e.g., a cellular connection) with the backbone provider network (orCloud). If a Mobile AP does not have such capability, the Mobile AP mayalso, for example, utilize data access provided by the end-user devicescommunicatively coupled thereto (e.g., leveraging the data plans of theend-user devices).

The third example mode 520 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the third example mode 520 may be utilized in anearly stage of a larger deployment, for example deployment that willgrow into another mode (e.g., the example first mode 500, example fourthmode 530, etc.) as more communication system equipment is installed.Note also that the third example mode 520 may be utilized in a scenarioin which the local infrastructure provider network and fixed hotspotaccess network are normally available but are currently unavailable(e.g., due to equipment failure, due to communication link failure, dueto power outage, due to a temporary denial of service, etc.).

The fourth example mode (or configuration) 530 (e.g., a no fixedhotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without thefixed hotspot access network and communication links therewith. Forexample, the communication system in the fourth example mode 530comprises a backbone provider network, a local infrastructure providernetwork, a mobile hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the fourth example mode 530 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), the end-userdevices, and/or environment devices via one or more wired links. Notethat such a wired coupling may be temporary. Also note that in variousexample configurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the fourth example mode 530 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Also note that in various exampleconfigurations, the backbone provider network may also becommunicatively coupled to the local infrastructure provider network viaone or more wireless (or non-tethered) links.

As additionally shown in FIG. 5B, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the fourth example mode 530(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wired links. Note that such a wired coupling may betemporary. Also note that in various example configurations, the localinfrastructure provider network may also, at least temporarily, becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof) via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the fourth example mode 530 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links.

The mobile hotspot access network is further shown in the fourth examplemode 530 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the fourth example mode 530 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the fourth example mode 530 (e.g., the no fixed hotspots mode),information (or data) may be communicated between an end-user device anda server via the mobile hotspot access network, the local infrastructureprovider network, and/or the backbone provider network. As will be seenin the various example modes presented herein, such communication mayflexibly occur between an end-user device and a server via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the local infrastructure provider networkand/or the backbone provider network (e.g., skipping the mobile hotspotaccess network). Also for example, information communicated between anend user device and a server may be communicated via the backboneprovider network (e.g., skipping the mobile hotspot access networkand/or local infrastructure provider network).

Similarly, in the fourth example mode 530 (e.g., the no fixed hotspotsavailable mode), information (or data) may be communicated between anenvironment device and a server via the mobile hotspot access network,the local infrastructure provider network, and/or the backbone providernetwork. Also for example, an environment device may communicate with orthrough an end-user device (e.g., instead of or in addition to themobile hotspot access network). As will be seen in the various examplemodes presented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network and/or backbone provider network)via any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the local infrastructure providernetwork and/or the backbone provider network (e.g., skipping the mobilehotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thebackbone provider network (e.g., skipping the mobile hotspot accessnetwork and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the mobile hotspot access network and/or backboneprovider network).

In the fourth example mode 530, in an example implementation, some ofthe control/management functions may for example be implemented withinthe local backbone provider network (e.g., within a client premises).For example, communication to the local infrastructure provider may beperformed through the backbone provider network (or Cloud). Note that ina scenario in which there is a direct communication pathway between thelocal infrastructure provider network and the mobile hotspot accessnetwork, such communication pathway may be utilized.

For example, since the mobile hotspot access network does not have acommunication link via a fixed hotspot access network, the Mobile APsmay utilize a direct connection (e.g., a cellular connection) with thebackbone provider network (or Cloud). If a Mobile AP does not have suchcapability, the Mobile AP may also, for example, utilize data accessprovided by the end-user devices communicatively coupled thereto (e.g.,leveraging the data plans of the end-user devices).

The fourth example mode 530 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the fourth example mode 530 may be utilized inan early stage of a larger deployment, for example a deployment thatwill grow into another mode (e.g., the example first mode 500, etc.) asmore communication system equipment is installed. The fourth examplemode 530 may, for example, be utilized in a scenario in which there isno fiber (or other) connection available for Fixed APs (e.g., in amaritime scenario, in a plantation scenario, etc.), or in which a FixedAP is difficult to access or connect. For example, one or more MobileAPs of the mobile hotspot access network may be used as gateways toreach the Cloud. The fourth example mode 530 may also, for example, beutilized when a vehicle fleet and/or the Mobile APs associated therewithare owned by a first entity and the Fixed APs are owned by anotherentity, and there is no present agreement for communication between theMobile APs and the Fixed APs. Note also that the fourth example mode 530may be utilized in a scenario in which the fixed hotspot access networkis normally available but are currently unavailable (e.g., due toequipment failure, due to communication link failure, due to poweroutage, due to a temporary denial of service, etc.).

The fifth example mode (or configuration) 540 (e.g., a no mobilehotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without themobile hotspot access network and communication links therewith. Forexample, the communication system in the fifth example mode 540comprises a backbone provider network, a local infrastructure providernetwork, a fixed hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the fifth example mode 540 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via one or more wired links. Note that such awired coupling may be temporary.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the fifth example mode 540 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Also note that in various exampleconfigurations, the backbone provider network may also becommunicatively coupled to the local infrastructure provider network viaone or more wireless (or non-tethered) links.

As additionally shown in FIG. 5B, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the fifth example mode 540(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), fixed hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wired links. Note that such a wired coupling may be temporary. Alsonote that in various example configurations, the local infrastructureprovider network may also, at least temporarily, be communicativelycoupled to the mobile hotspot access network (or any component thereof)via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the fifth example mode 540 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network, the fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via one or more wireless links. Note that thecommunication link(s) shown in the fifth example mode 540 of FIG. 5Bbetween the local infrastructure provider network and the fixed hotspotaccess network may be wired and/or wireless.

The fixed hotspot access network is also shown in the fifth example mode540 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the fifth example mode 540 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the fifth example mode 540 (e.g., the no mobile hotspots availablemode), information (or data) may be communicated between an end-userdevice and a server via the fixed hotspot access network, the localinfrastructure provider network, and/or the backbone provider network.As will be seen in the various example modes presented herein, suchcommunication may flexibly occur between an end-user device and a servervia any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc. For example, information communicated between anend user device and a server may be communicated via the localinfrastructure provider network, and/or the backbone provider network(e.g., skipping the fixed hotspot access network). Also for example,information communicated between an end user device and a server may becommunicated via the backbone provider network (e.g., skipping the fixedhotspot access network and/or local infrastructure provider network).

Similarly, in the fifth example mode 540 (e.g., the no mobile hotspotsavailable mode), information (or data) may be communicated between anenvironment device and a server via the fixed hotspot access network,the local infrastructure provider network, and/or the backbone providernetwork. Also for example, an environment device may communicate with orthrough an end-user device (e.g., instead of or in addition to the fixedhotspot access network). As will be seen in the various example modespresented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network and/or backbone provider network)via any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the local infrastructure providernetwork and/or the backbone provider network (e.g., skipping the fixedhotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thebackbone provider network (e.g., skipping the fixed hotspot accessnetwork and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the fixed hotspot access network and/or the backboneprovider network).

In the fifth example mode 540, in an example implementation, theend-user devices and environment devices may communicate directly toFixed APs (e.g., utilizing Ethernet, Wi-Fi, etc.). Also for example, theend-user devices and/or environment devices may communicate directlywith the backbone provider network (e.g., utilizing cellularconnections, etc.).

The fifth example mode 540 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation in which end-user devices and/or environmentdevices may communicate directly with Fixed APs, such communication maybe utilized instead of Mobile AP communication. For example, the fixedhotspot access network might provide coverage for all desired areas.

Note also that the fifth example mode 540 may be utilized in a scenarioin which the fixed hotspot access network is normally available but iscurrently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

The sixth example mode (or configuration) 550 (e.g., the no fixed/mobilehotspots and local infrastructure available mode) may, for example,share any or all characteristics with the first example mode 500, albeitwithout the local infrastructure provider network, fixed hotspot accessnetwork, mobile hotspot access network, and communication linkstherewith. For example, the communication system in the sixth examplemode 550 comprises a backbone provider network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the sixth example mode 550 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the end-user devicesand/or environment devices via one or more wired links. Note that such awired coupling may be temporary.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the sixth example mode 550 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the end-user devices and/or environmentdevices via one or more wireless links.

The end-user devices are also shown in the sixth example mode 550 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the sixth example mode 550 (e.g., the no fixed/mobile hotspots andlocal infrastructure available mode), information (or data) may becommunicated between an end-user device and a server via the backboneprovider network. Similarly, in the sixth example mode 550 (e.g., the nofixed/mobile hotspots and local infrastructure mode), information (ordata) may be communicated between an environment device and a server viathe backbone provider network. Also for example, an environment devicemay communicate with or through an end-user device (e.g., instead of orin addition to the mobile hotspot access network).

The sixth example mode 550 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, for example in which an end-user has not yetsubscribed to the communication system, the end-user device maysubscribe to the system through a Cloud application and by communicatingdirectly with the backbone provider network (e.g., via cellular link,etc.). The sixth example mode 550 may also, for example, be utilized inrural areas in which Mobile AP presence is sparse, Fixed AP installationis difficult or impractical, etc.

Note also that the sixth example mode 550 may be utilized in a scenarioin which the infrastructure provider network, fixed hotspot accessnetwork, and/or mobile hotspot access network are normally available butare currently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

The seventh example mode (or configuration) 560 (e.g., the no backboneand mobile hotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without thebackbone provider network, mobile hotspot access network, andcommunication links therewith. For example, the communication system inthe seventh example mode 560 comprises a local infrastructure providernetwork, fixed hotspot access network, end-user devices, and environmentdevices.

As shown in FIG. 5C, and in FIG. 1 in more detail, the localinfrastructure provider network may be communicatively coupled to any orall of the other elements present in the seventh example mode 560 (orconfiguration) via one or more wired (or tethered) links. For example,the local infrastructure provider network may be communicatively coupledto the fixed hotspot access network (or any component thereof), theend-user devices, and/or environment devices via one or more wiredlinks. Note that such a wired coupling may be temporary.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the seventh example mode 560 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Note that the communication link shown inthe seventh example mode 560 of FIG. 5C between the local infrastructureprovider network and the fixed hotspot access network may be wiredand/or wireless.

The fixed hotspot access network is also shown in the seventh examplemode 560 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Additionally, the end-userdevices are also shown in the seventh example mode 560 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the seventh example mode 560 (e.g., the no backbone and mobilehotspots available mode), information (or data) may be communicatedbetween an end-user device and a server via the fixed hotspot accessnetwork and/or the local infrastructure provider network. As will beseen in the various example modes presented herein, such communicationmay flexibly occur between an end-user device and a server via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the fixed hotspot access network).

Similarly, in the seventh example mode 560 (e.g., the no backbone andmobile hotspots available mode), information (or data) may becommunicated between an environment device and a server via the fixedhotspot access network and/or the local infrastructure provider network.Also for example, an environment device may communicate with or throughan end-user device (e.g., instead of or in addition to the mobilehotspot access network). As will be seen in the various example modespresented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network) via any of a variety of differentcommunication pathways, for example depending on the availability of anetwork, depending on bandwidth utilization goals, depending oncommunication priority, depending on communication time (or latency)and/or reliability constraints, depending on cost, etc. For example,information communicated between an environment device and a server maybe communicated via the local infrastructure provider network (e.g.,skipping the fixed hotspot access network).

The seventh example mode 560 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample controlled space implementation, Cloud access might not beprovided (e.g., for security reasons, privacy reasons, etc.), and full(or sufficient) coverage of the coverage area is provided by the fixedhotspot access network, and thus the mobile hotspot access network isnot needed. For example, the end-user devices and environment devicesmay communicate directly (e.g., via Ethernet, Wi-Fi, etc.) with theFixed APs

Note also that the seventh example mode 560 may be utilized in ascenario in which the backbone provider network and/or fixed hotspotaccess network are normally available but are currently unavailable(e.g., due to equipment failure, due to communication link failure, dueto power outage, due to a temporary denial of service, etc.).

The eighth example mode (or configuration) 570 (e.g., the no backbone,fixed hotspots, and local infrastructure available mode) may, forexample, share any or all characteristics with the first example mode500, albeit without the backbone provider network, local infrastructureprovider network, fixed hotspot access network, and communication linkstherewith. For example, the communication system in the eighth examplemode 570 comprises a mobile hotspot access network, end-user devices,and environment devices.

As shown in FIG. 5C, and in FIG. 1 in more detail, the mobile hotspotaccess network is shown in the eighth example mode 570 to becommunicatively coupled to the end-user devices and/or environmentdevices via one or more wireless links. Many examples of such wirelesscoupling are provided herein. Further, the end-user devices are alsoshown in the eighth example mode 570 to be communicatively coupled tothe environment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein.

In the eighth example mode 570 (e.g., the no backbone, fixed hotspots,and local infrastructure available mode), information (or data) mightnot (at least currently) be communicated between an end-user device anda server (e.g., a coupled to the backbone provider network, localinfrastructure provider network, etc.). Similarly, information (or data)might not (at least currently) be communicated between an environmentdevice and a server (e.g., a coupled to the backbone provider network,local infrastructure provider network, etc.). Note that the environmentdevice may communicate with or through an end-user device (e.g., insteadof or in addition to the mobile hotspot access network).

The eighth example mode 570 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the eighth example mode 570 may be utilized forgathering and/or serving data (e.g., in a delay-tolerant networkingscenario), providing peer-to-peer communication through the mobilehotspot access network (e.g., between clients of a single Mobile AP,between clients of respective different Mobile APs, etc.), etc. Inanother example scenario, the eighth example mode 570 may be utilized ina scenario in which vehicle-to-vehicle communications are prioritizedabove vehicle-to-infrastructure communications. In yet another examplescenario, the eighth example mode 570 may be utilized in a scenario inwhich all infrastructure access is lost (e.g., in tunnels, parkinggarages, etc.).

Note also that the eighth example mode 570 may be utilized in a scenarioin which the backbone provider network, local infrastructure providernetwork, and/or fixed hotspot access network are normally available butare currently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

As shown and discussed herein, it is beneficial to have a genericplatform that allows multi-mode communications of multiple users ormachines within different environments, using multiple devices withmultiple technologies, connected to multiple moving/static things withmultiple technologies, forming wireless (mesh) hotspot networks overdifferent environments, connected to multiple wired/wirelessinfrastructure/network backbone providers, ultimately connected to theInternet, Cloud or private network infrastructure.

FIG. 6 shows yet another block diagram of an example networkconfiguration, in accordance with various aspects of the presentdisclosure. The example network 600 may, for example, share any or allcharacteristics with the other example methods, networks and/or networkcomponents 100, 200, 300, 400, 500-570, 700, 800, 900, 1000, 1100, 1200,1300, 1400, and 1500, discussed herein. Notably, the example network 600shows a plurality of Mobile APs (or OBUs), each communicatively coupledto a Fixed AP (or RSU), where each Mobile AP may provide network accessto a vehicle network (e.g., comprising other vehicles or vehiclenetworks, user devices, sensor devices, etc.).

FIG. 7 shows still another block diagram of an example communicationnetwork 700, in accordance with various aspects of the presentdisclosure. The example network 700 may, for example, share any or allcharacteristics with the other example methods, networks and/or networkcomponents 100, 200, 300, 400, 500-570, 600, 800, 900, 1000, 1100, 1200,1300, 1400, and 1500, discussed herein. Notably, the example network 700shows a plurality of vehicles (or Mobile APs, or MAPs, or OBUs) 752,754, 756, and 758, each communicatively coupled to a Fixed AP (or RSU)742, 744, and 748 and/or a cellular network 706, where each Mobile APmay provide network access to a vehicle network (e.g., comprising othervehicles or vehicle networks, user devices, sensor devices, etc.), forexample a Wi-Fi network to which end user devices may connect, withwhich communication with sensors may be performed, etc. The vehiclesmay, for example, be autonomous vehicles, vehicles controlled by a localoperator, vehicles controlled by a remote operator, etc. The examplenetwork 700 may also, for example, comprise a plurality of NetworkControllers 732, 734, and 738. The example network 700 may also, forexample, comprise any of a variety of interconnected networks (e.g.,Private Networks 702, the Internet 704, Telecommunication Networks 706,etc.). One or more servers of the Cloud may, for example, be accessiblevia Cloud APIs 760.

The Mobile APs 752, 754, 756, and 758 may, for example, becommunicatively coupled to various sensors (e.g., always, as the MobileAPs travel within range of such sensors, etc.). For example, in theexample scenario shown in FIG. 7, a first MAP 752 is communicativelycoupled to a first sensor 771 (e.g., Sensor 1) and a set of sensors 772(e.g., Sensor 2, Sensor 3, Sensor 4, and Sensor 5), which may forexample be co-located; a second MAP 754 is communicatively coupled to asixth sensor 773; and an M^(th) MAP 758 is communicatively coupled to aseventh sensor 774. The Mobile APs may, for example move in and out ofcommunication range of the various sensors. The Mobile APs may, forexample when in-range of such sensors, gather information from suchsensors in a power-efficient and network-efficient manner, many examplesof which are provided herein.

As discussed herein, mobile Access Points (APs) can efficiently receiveand/or transmit a large variety of information, for example fromsensors, from user client devices, from enterprises along a vehicleroute, etc. To efficiently receive data from data sources and transportthe received data to the Cloud, a communication network in accordancewith various aspects of this disclosure (e.g., a network or Internet ofMoving Things) may be utilized as a communication backbone. For example,in an example implementation, a vehicle equipped with a Mobile AP (orOBU) can receive data from an information source (e.g., a sensor, localarea network, user client device, etc.) as the vehicle carries, passesby, or parks nearby the information source. Received data can be storedand processed and made available to/from the Cloud (e.g., via APIs orother interface) or to any node in the network. As an example,non-limiting examples of systems and methods for collecting sensor data,for example in a network of moving things, are provided in U.S.Provisional Application No. 62/222,135, titled “SYSTEMS AND METHODS FORCOLLECTING SENSOR DATA IN A NETWORK OF MOVING THINGS,” filed on Sep. 22,2015, the entire content of which is hereby incorporated herein byreference.

In accordance with various aspects of the present disclosure, systemsand methods are provided that utilize one or more mobile access pointsto receive data (or information). Various aspects of this disclosureprovide for cooperation among Mobile APs and one or more communicationnetworks to optimize the communication of various types of data to adestination (e.g., an application executing on a computer (or server) inthe Cloud, an application executing on a network node, etc.). Such datacommunication may, for example, be adjusted dynamically in response tovarious conditions (e.g., network availability, delivery time goals,network congestion, Mobile AP location and/or expected trajectory, time,day, emergency conditions, various external events, etc.). Such datacommunication may, for example, comprise transporting the data to theCloud or any other node in various ways (e.g., utilizing any of avariety of communication technologies, utilizing any of a variety ofpathways through the network, utilizing delay-tolerant networking (DTN),utilizing opportunistic uploads, for example via Wi-Fi networksaccessible to a Mobile AP (e.g., while moving, while stationary, etc.),utilizing cellular network communication if necessary or desired, etc.).

In a network in which mobile nodes (e.g., Mobile APs, user devices,etc.) are utilized to receive (or collect or gather) data, sources ofsuch data may be numerous and the volume of such data may be great. Overtime, it is expected that the network of moving things will result in arapid increase in the amount of data received and/or communicated (e.g.,in a metropolitan area, etc.). Such increases in the volume of data,however, present data collecting, storage, processing, and communicationchallenges.

In an example scenario in which there is too much data for one or moreMobile APs to handle, some data may be lost (e.g., not collected at all,only partially collected, collected with errors, etc.). Other data maybe collected, but not in a timely manner. For example, a Mobile AP mayfail or be overwhelmed if operated autonomously in accordance with aninflexible data collection strategy (or plan). Fortunately, a network ofmoving things provides the flexibility and/or adaptability needed torespond to unforeseen system disturbances, data collecting and/orcommunicating needs, system and/or sensor topology changes, etc. Suchflexibility may, for example, provide for the necessary or desiredamount of data to be received and/or communicated to a destination.

A communication network, or portion thereof, constructed and/or operatedin accordance with various aspects of the present disclosure providesmany benefits, non-limiting examples of which include the utilization(or exploitation) of opportunistic communication. For example, forvarious types of data (e.g., data associated with no real-time deliveryurgency, etc.) may be communicated utilizing networks encountered duringa Mobile AP's travels (e.g., a Wi-Fi network available to the Mobile APas the Mobile AP drives through and/or or parks in the coverage area ofthe Wi-Fi network, etc.). Note that such communication may occur in bothupstream and downstream directions.

Also for example, a Mobile AP may receive information to communicateupstream, but might not presently be in communication range of a FixedAP of the vehicle network. In such a scenario, for example in which thedata need not be communicated upstream immediately, the Mobile AP maystore the received data and wait to be within range of a Fixed AP, forexample instead of utilizing the cellular network. Additionally, asdiscussed herein, the Mobile AP may communicate the received data toother Mobile APs for their assistance with the communication of suchdata.

Such opportunistic communication may reduce data communication costs,for example utilizing free (or cheap) access to Wi-Fi networks ratherthan consuming communication bandwidth of the vehicle communicationnetwork in which Mobile APs typically operate and/or rather than payingthe costs associated with the communication of data over the cellularcommunication network. Additionally, such opportunistic communicationmay reduce bandwidth consumption of cellular networks, which is limitedand shared among several devices.

A system and/or method implemented in accordance with various aspects ofthis disclosure may, for example, incorporate store-and-forwardmechanisms (or techniques) to assist with the opportunisticcommunication of data. For example, data may be replicated to performupstream and/or downstream communication of data within the network.Though as discussed herein, cellular network utilization tends to beexpensive, various aspects of this disclosure still comprise theflexible utilization of cellular network communication when necessary ordesired.

Turning to FIG. 8, such figure shows a block diagram of a system 800 andmethod at a node for delay tolerant networking, in accordance withvarious aspects of the present disclosure. The example system 800 may,for example, share any or all characteristics with the other examplemethods, networks and/or network components 100, 200, 300, 400, 500-570,600, 700, 900, 1000, 1100, 1200, 1300, 1400, and 1500, discussed herein.Any or all of the aspects of FIG. 8 (e.g., any or all of the blocksand/or portions thereof) may be implemented in a node of a communicationnetwork (e.g., a Mobile AP or OBU, etc.). For example, the system 800may be implemented in a Mobile AP or other network node.

The example system 800 may, for example, comprise an Application ProgramInterface (API) 810 via which the system 800 (e.g., a node or portionthereof) may send and/or receive data to and/or from the delay tolerantnetwork (DTN). For example, applications executing on a node may utilizethe API 810 to perform reception and/or transmission of data packets.

For example, in an example implementation, an application that desiresto send data may provide a destination and a service identifier to theAPI. Also for example, an application that desires to receive data may,for example, just register a service identifier. Note that suchapplication may also, in various scenarios, specify source identityinformation.

The example system 800 (e.g., a Mobile AP, etc.) may, for example,comprise a Receive block 820 (or module) that is operable to receivepackets transmitted by other nodes within range of the node (e.g., peernodes, Mobile AP nodes, Fixed AP nodes, sensor nodes, user client nodes,Network Controller nodes, network infrastructure nodes, cellular nodes,network access points, etc.).

The example system 800 may, for example, comprise a Storage block 830(or module). The Storage block 830 may, for example, implement permanentand/or temporary caching of received data. For example, in a scenario inwhich received data is to be forwarded (e.g., upstream, downstream,etc., including to peer nodes), the Storage block 830 may manage thememory utilized for such caching (e.g., memory allocation, writing,reading, memory deallocation, etc.). For example, the Storage block 830may be operable to store data until the data is successfullycommunicated to its destination, until the data is successfullycommunicated to all desired destinations, until the data expires, etc.).

The example system 800 may, for example, comprise a Neighboring (orNeighboring Node) block 840 (or module) that is operable to maintain anupdated list of neighbor nodes in the area of the system 800. Forexample, in an example implementation in which the system 800 isimplemented in a Mobile AP, the Neighboring block 840 may operate tomaintain a list of nodes (e.g., Mobile AP nodes, Fixed AP nodes, sensornodes, Wi-Fi access point nodes, cellular base station nodes, userclient nodes, etc.) that are believed to be in communication range ofthe Mobile AP.

The example system 800 may, for example, comprise a Routing block 850(or module) that is operable to perform any or all of the communicationrouting discussed herein (e.g., the routing of data to peer nodes (e.g.,peer Mobile AP nodes, etc.), the routing of information to vehiclecommunication network infrastructure components (e.g., Fixed AP nodes ofthe vehicle or mobile network, etc.), opportunistic routing ofinformation to Wi-Fi networks, routing of information to a cellularnetwork, etc.

In an example implementation, the Routing block 850 may operate toconsider available neighbor nodes (e.g., of a list maintained by theNeighboring block 840, etc.), the stored data and its destination, anumber of replications desired and/or allowed, time, signal strength,estimated travel routes of other nodes, network connectivity of othernodes, fleet associations of other nodes, bandwidth utilization of othernodes, etc., when determining other nodes to which the data is to betransmitted. Note that such routing determinations may be different whencommunicating (or uploading) data to the Cloud (e.g., to a Cloud serveror database) versus disseminating (or downloading) data to another node,or any or all nodes, throughout the network.

In accordance with various aspects of the present disclosure, data(e.g., a data packet, file, etc.) may be associated with a lifetime. Insuch an example implementation, when data has reached its lifetime, thedata may be dropped and/or sent through a cellular network. In anexample implementation, each data packet (or record, or file, etc.) maybe assigned a lifetime, a delivery deadline, a priority ranking, anindication of whether cellular network utilization is authorized forfault-back (or fail-safe) communication, etc.

FIG. 9 shows a block diagram of a system and method in a mobile networkfor delay tolerant networking, in accordance with various aspects of thepresent disclosure. The example system (or network) of FIG. 9 may, forexample, share any or all characteristics with the other examplemethods, networks and/or network components 100, 200, 300, 400, 500-570,600, 700, 800, 1000, 1100, 1200, 1300, 1400, and 1500, discussed herein.The illustration 900 of FIG. 9 shows an example manner in which a MobileAP may communicate (e.g., upload) data to the Cloud (e.g., to a server,an application being executed by a server, etc.).

The example illustration 900 shows three distinct moments in time, inparticular: T0, T1 and T2. At time T0, the Mobile AP 910 has fourpackets stored, but is only able to send two packets (e.g., packet 1 andpacket 2) through a first Fixed AP 921 of the system (or network). Thefirst Fixed AP 921, in turn, communicates the first two packets (e.g.,packet 1 and packet 2) to the Cloud 930 (e.g., a Cloud server, database,central controller, etc.). The Mobile AP 910 removes the first twopackets from memory and continues to store the other two packets (e.g.,packet 3 and packet 4). In an example scenario, the Mobile AP 910 mayfor example receive an ACK from the Cloud (e.g., via the first Fixed AP921, etc.) indicating that the first two packets were successfullyreceived by the ultimate destination, at which point the Mobile AP 910may remove the first two packets from memory. In another examplescenario, the Mobile AP 910 may assume that since the first two packetswere delivered successfully to the first Fixed AP 921, the packets willbe delivered to their ultimate destination successfully, and then removethe first two packets from memory.

At time T1, the Mobile AP 910′ still has packet 3 and packet 4 stored,but has also received (or generated) two more packets to communicate(e.g., packet 5 and packet 6). At time T1, the Mobile AP 910′ is unableto communicate any of the stored packets to the network, so continues tostore such packets.

At time T2, the Mobile AP 910″ is in range of the second Fixed AP 922and sends all of the stored packets (e.g., packet 3, packet 4, packet 5,and packet 6) to the Cloud 930 via the second Fixed AP 922.

FIG. 10 shows a block diagram of a system and method in a mobile networkfor delay tolerant networking, in accordance with various aspects of thepresent disclosure. The example system 1000 may, for example, share anyor all characteristics with the other example methods, networks and/ornetwork components 100, 200, 300, 400, 500-570, 600, 700, 800, 900,1100, 1200, 1300, 1400, and 1500, discussed herein. The illustration1000 of FIG. 10 shows an example manner in which a Mobile AP maydisseminate (e.g., or download or laterally propagate) data from theCloud (e.g., to other Mobile APs, etc.).

The example illustration 1000 shows three distinct moments in time, inparticular: T0, T1 and T2. At time T0, the first Mobile AP 1011 receivesthree packets (e.g., packet 1, packet 2, and packet 3) from the Cloud1030 via the Fixed AP 1020, for example when the first Mobile AP 1011travels within range of the Fixed AP 1020. The first Mobile AP 1011 thenstores the received three packets until such packets can be communicatedto the other Mobile APs (e.g., the second Mobile AP 1012 and the thirdMobile AP 1013), for example when such other Mobile APs are withincommunication range of the first Mobile AP 1011′.

At time (or time window) T1, the first Mobile AP 1011′ (e.g., throughthe first Mobile AP 1011 moving and/or the second Mobile AP 1012 andthird Mobile AP 1013 moving) comes within range of the second Mobile AP1012′ and the third Mobile AP 1013′, which are destinations for thedata. The first Mobile AP 1011′ successfully communicates the threepackets to the second Mobile AP 1012′, but only successfullycommunicates the first and second packets to the third Mobile AP 1013′.For example, the first Mobile AP 1011′ and the third Mobile AP 1013′might not have been in communication range long enough to successfullycommunicate all three packets.

At time T2, the third Mobile AP 1013″ is now within communication rangeof the second Mobile AP 1012″. For example, the third Mobile AP 1013″may determine that it is within range of the second Mobile AP 1012″ byanalyzing a signal transmitted by the third Mobile AP 1013″, byanalyzing vehicle location information (e.g., as received from apositioning system, from an autonomous vehicle control system, etc.).The second Mobile AP 1012″ completes the communication of the threepackets to the third Mobile AP 1013″ by communicating the third packetto the third Mobile AP 1013″. At this point, all three of the exampleMobile APs have successfully received the three packets from the Cloud1030. In an example implementation, the Mobile APs may communicate witheach other to determine the present state of the packet transfer. Forexample, Mobile APs that encounter each other may discuss whether eachof such Mobile APs has fully received particular data.

Note that the Mobile APs may also indicate information characterizingthe data being propagated. For example, such data may have a versionnumber, publishing date, etc. In such a scenario, Mobile APs may worktogether to ensure that they each have the latest updates toinformation.

FIG. 11 shows a block diagram of a system and method at a node for delaytolerant networking, in accordance with various aspects of the presentdisclosure. The example system and method 1100 may, for example, shareany or all characteristics with the other example methods, networksand/or network components 100, 200, 300, 400, 500-570, 600, 700, 800,900, 1000, 1200, 1300, 1400, and 1500, discussed herein. FIG. 11 may,for example, show various processes that may be implemented by theRouting block and the Receive block discussed herein.

The example system and method 1100 may, for example, comprise a Receiveblock 1102. The Receive block 1102 may comprise any of a variety ofcharacteristics, non-limiting examples of which are provided herein.

In an example implementation, the Receive block 1102 may comprise thecapability to distinguish a received data packet from an acknowledgment(ACK) packet. If the received packet is a data packet (e.g., asdetermined at block 1140), the node may store the packet in memory(e.g., at block 1160), for example after verifying that the data packetis not already stored in memory. The Receive block 1102 may also (e.g.,at block 1150) communicate an ACK packet at to the node that sent thedata packet (e.g., a peer node, an original source node, etc.),confirming that the data packet was successfully received. If, however,the received packet is an ACK packet from a neighbor (e.g., asdetermined at block 1170), the node may (e.g., at block 1180) mark thestored data packet to which the ACK corresponds as delivered to thatneighbor (e.g., in a case in which the data is being disseminated in thenetwork, distributed to particular other nodes, etc.). Also for example,the node may delete the data packet (e.g., at block 1180) to which theACK corresponds from storage (e.g., when the node determines that itsdistribution of the data packet has been completed).

Note that the ACK or related information may be disseminated in thenetwork in an example scenario in which the ACK is originated by theultimate destination for the data (e.g., an application executing on aserver in the Cloud, etc.). For example, in an example scenario in whicha Mobile AP has propagated data to other Mobile APs in an attempt tocommunicate the data to a Cloud destination, receipt of an ACK thatoriginated from the Cloud destination may cause dissemination of the ACKto the other Mobile APs that received the propagated data. Suchcommunication may, for example, reduce the amount of redundantcommunication of the propagated data. In another example scenario, forexample in which a Mobile AP successfully delivers the data to a FixedAP and receives the ACK from the Fixed AP, the Mobile AP may assume thatsubsequent delivery of the data is guaranteed and thus purge the datafrom its storage. In an example scenario, the network may flood thenetwork (or a portion thereof, for example under one or more particularFixed APs) with such ACK. In another example scenario, the network maypropagate the ACK in the same manner as the network disseminates datapackets, as discussed herein.

The example system and method 1100 may also, for example, comprise aRouting block 1105. The Routing block 1105 may comprise any of a varietyof characteristics, non-limiting examples of which are provided herein.

The Routing block 1105 may, for example, determine the node(s) to whichthe received data will be sent. To make this determination (e.g., atblock 1110), the Routing block 1105 may consider many factors, forexample whether a network access point (e.g., a Wi-Fi hot spot AP,vehicle communication network Fixed AP, other Mobile APs, etc.) is incommunication range, the delivery requirements (e.g., time constraints,priority, guaranteed/not, etc.) associated with the data, the lifetimeof the data, etc. In an example scenario, the Routing block 1105 mayretrieve the data from storage (e.g., at block 1120) if necessary, andsend the data (e.g., at block 1130). In an example implementation, theRouting block 1105 may (e.g., at block 1130) send the data to a Wi-Fihot spot AP if available, else send the data to a Fixed AP of thevehicle communication network if available, else send the data to one ormore other Mobile APs if available, and may ultimately send the data toa destination utilizing a cellular link if time and/or priorityconstraints warrant such action. In a scenario in which the Routingblock 1105 decides to send the data to one or more other Mobile APs, theRouting block 1105 may identify (e.g., at block 1130) the best Mobile AP(or N best Mobile APs) to which the Routing block 1105 should send thedata.

FIG. 12 shows a block diagram of a system and method in a mobile networkfor delay tolerant networking, in accordance with various aspects of thepresent disclosure. The example system 1200 may, for example, share anyor all characteristics with the other example methods, networks and/ornetwork components 100, 200, 300, 400, 500-570, 600, 700, 800, 900,1000, 1100, 1300, 1400, and 1500, discussed herein.

For example, as discussed herein, the respective functionalities of theblocks presented herein may be implemented in any node of the network.Accordingly, the capability is provided to have an end-to-end DTNbetween any two nodes in the network, for example between two userclient devices, between a sensor and a Cloud server, between any twocommunication network nodes, etc. In an example implementation, theend-to-end DTN functionality is accomplished by incorporating all of theDTN functionality into each node, even for example end user client orsensor nodes. In another example implementation, the end-to-end DTNfunctionality is generally accomplished by incorporating all (or mostall) of the DTN functionality into each node of the vehicle network,providing a convenient interface to end devices (e.g., sensor devices,user client devices, etc.) desiring to utilize the DTN capabilities ofthe network.

The example method, system, and/or network 1200 may, for example, beimplemented as a dynamic mesh network (e.g., at least at the Mobile APlevel) that comprises multi-hop capability and multi-homing (orlocation) capability in the vehicle (or mobile) network (e.g., in MobileAPs, in Fixed APs, etc.). User devices and/or sensors may, for example,communicate with the vehicle (or mobile) network via Wi-Fi or other WLANor WPAN connections. In an example implementation, each device may beassociated with an identification within the network. Routingfunctionality may generally, for example, be implemented by nodes of thevehicle (or mobile) network (e.g., by the Mobile APs and/or Fixed APs)to update data to the Cloud or to disseminate data throughout thevehicle (or mobile) network. For example, the source and destinationendpoints may simply communicate the information to a node of thevehicle (or network) network and then rely on the network to perform thecommunication.

In an example delay tolerant networking implementation, the DTNfunctionality may, for example, be performed at a layer above the OSIlayer 2 (MAC layer), for example inside the vehicular network throughDSRC. For example, the DTN protocol (or portions thereof) may beimplemented at the Operating System (OS) level. Various aspects of theDTN protocol may also be implemented at the OSI layer 4 (Transportlayer), for example to exchange data with DTN servers and to be able touse all available interfaces of different communication technologies.

In an example implementation, DTN servers may be implemented in theCloud to absorb DTN traffic peaks. For example, such DTN servers mayunderstand the DTN protocol and may thus be able to translate to otherprotocols to store data in the Cloud databases (DBs).

In the example 1200 shown in FIG. 12, a sensor 1250 having sensor datato upload to the Cloud communicates such sensor data to the first MobileAP 1211 of the vehicle network 1240, which communicates such sensor datato a Fixed AP 1220 of the vehicle network 1240, which communicates suchsensor data to a DTN server 1232 of the Cloud 1230, which communicatessuch sensor data to a database 1235 of the Cloud 1230.

Also in the example 1200 shown in FIG. 12, a first user device 1261having user data to disseminate in the network communicates such userdata to the first Mobile AP 1211 of the vehicle network 1240, whichcommunicates such user data to a third Mobile AP 1213 of the vehiclenetwork 1240, which communicates such user data to a second Mobile AP1212 of the vehicle network 1240. The third Mobile AP 1213 communicatessuch sensor data to a third user device 1263, and the second Mobile AP1212 communicates such sensor data to a second user device 1262.

FIG. 13 shows a block diagram of a method 1300 for performing delaytolerant networking, for example in a node, in accordance with variousaspects of the present disclosure. The example method 1300 and systemmay, for example, share any or all characteristics with the otherexample methods, networks and/or network components 100, 200, 300, 400,500-570, 600, 700, 800, 900, 1000, 1100, 1200, 1400, and 1500, discussedherein. The example method 1300 or any portion thereof may, for example,be implemented in any network node discussed herein (e.g., a Mobile APor OBU, etc.). The example method 1300 may also incorporate any or allof the functionality discussed herein.

The example method 1300 may begin executing at block 1305. At block1310, data to be propagated upstream to the Cloud (e.g., to anapplication running on a computer or server in the Cloud) is received.The received data is stored at block 1320.

In the example implementation, it is determined that for at least a timeT₁, the preferred form of communication for the data will be throughopportunistic utilization of a Wi-Fi network. For example, a Mobile APimplementing the method 1300 may store the data, continually looking foran accessible Wi-Fi network (e.g., a publicly available Wi-Fi hot spot,etc.) via which the Mobile AP may communicate the data to or toward itsultimate destination.

Although not specifically shown in the method 1300, different levels ofsecure communication may be utilized for communicating the data based onthe communication pathway utilized. For example, communication ofsensitive data via the public Internet may be performed utilizing ahigher degree of data protection (e.g., encryption, etc.), while datacommunicated via a closed vehicle network may be communicated with alower degree of data protection.

If the time threshold T₁ is exceeded and the data has not yet beensuccessfully communicated, then the method 1300, at block 1340, adds asecond network communication possibility, in particular the vehicle (ormobile) network infrastructure (e.g., Fixed APs, etc.). Accordingly,until time T₂ is exceeded, the node will utilize a Wi-Fi hotspot or thevehicle network to communicate the data, whichever is available first.For example, if a Mobile AP detects a Wi-Fi hotspot through which theMobile AP may communicate the data to its destination, then the MobileAP will attempt to communicate the data in such manner. Also forexample, if a Mobile AP detects a Fixed AP of the vehicle network, thenthe Mobile AP will attempt to communicate the data in such manner.

If the time threshold T₂ is exceeded and the data has not yet beensuccessfully communicated, then the example method 1300, at block 1350,propagates the data to other Mobile APs, for example to increase theodds that some carrier of the data will encounter a network (e.g., aWi-Fi hotspot, a vehicle network Fixed AP, etc.) over which the data canbe communicated. Block 1350 may comprise performing such propagation inany of a variety of manners. For example, block 1350 may comprisedetermining how many Mobile APs and/or which APs to send the data. Theremay, for example, be a target (or maximum) number of Mobile APs based onhop count. For example, in a scenario in which a Mobile AP was asingle-hop recipient of the data, the Mobile AP may communicate the datato N (e.g., 3 or 4, etc.) other Mobile APs. Also for example, in ascenario in which a Mobile AP was a second-hop recipient of the data(e.g., receiving the data from another Mobile AP), the Mobile AP maycommunicate the data to M (e.g., 1 or 2) other Mobile APs. Additionallyfor example, in a scenario in which a Mobile AP was a third-hoprecipient of the data, the Mobile AP might determine that it is notallowed by the propagation protocol to further propagate the data.

In an example scenario in which a Mobile AP may communicate the data tofour other Mobile APs, the Mobile AP may select the first four otherMobile APs with the strongest signal strength. Also for example, theMobile AP may select another Mobile AP that is known to be in a coveragearea of an available Wi-Fi hotspot and/or a Fixed AP of the vehiclenetwork. Additionally for example, the Mobile AP may select anotherMobile AP that has a location and a trajectory that will soon lead suchMobile AP into a coverage area of a Fixed AP of the vehicle network.

Until the time threshold T₃ is exceeded and if the data has not yet beensuccessfully communicated, then the method 1300, at block 1360,continues to attempt to utilize a Wi-Fi hotspot or the vehicle networkto communicate the data, whichever is available first. Note that in thiscase, a plurality of other Mobile APs may similarly be attempting tocommunicate the same data to the same ultimate destination. For example,if any of the Mobile APs detects a Wi-Fi hotspot through which theMobile AP may communicate the data to its destination, then the MobileAP will attempt to communicate the data in such manner. Also forexample, if any of the Mobile APs detects a Fixed AP of the vehiclenetwork, then the Mobile AP will attempt to communicate the data in suchmanner.

If the time threshold T₃ is exceeded and the data has not yet beensuccessfully communicated (at least as far as is known by the nodeimplementing the method 1300), then the method 1300, at block 1370,communicates the data utilizing the cellular network. In this case, thecellular network is utilized as a safety net (or fault-over) forcommunication of the data (albeit an expensive alternative generally).Though not shown, a determination may be made to drop the data and notcommunicate the data. For example, if it is determined that the data isnot important enough to warrant utilization of the cellular network, thedecision may be made to clear the data from memory and refrain fromfurther attempting to communicate it. For example, particular data maybe classified as loss-tolerant, and may also be flagged to utilize onlylow-cost communication pathways for the communication of such data, forexample deleting the data if such low-cost communication is notavailable. In an example implementation, when data is received by aMobile AP, information received with the data may indicate that the datamay only be communicated via a Wi-Fi hot spot and the vehicle network,and that the data has a lifetime of three hours after which it should bedropped, even if not further communicated.

At block 1380, the example method 1300 may comprise clearing (orremoving) the data from memory. For example, block 1380 may comprisede-allocating memory in which the data was stored and/or removing areference to the data from a list of data to communicate. Note that eachnode may comprise a list of data to communicate, and such list may beprioritized (e.g., based on type of data, based on data deliverydeadlines, based on data lifetime, based on client or customer priority,etc.).

As discussed herein, various decisions (e.g., routing decisions, storagedecisions, propagating decisions, etc.) may be made based on variousparameters or factors (e.g., time constraints, data priority orimportance, number of other Mobile APs to utilize, identify of networksto utilize, etc.). Such parameters may be communicated to the node inany of a variety of manners. For example, the original data communicatedto the node may include information (e.g., in packet fields, headerfields, meta data, etc.) identifying the parameters for the data. Forexample, a data packet communicating the data or a portion thereof mayindicate a maximum allowable guaranteed delivery time, at which pointthe cellular network must be utilized. Also for example, such a datapacket may indicate how many Mobile APs may receive replicates of thedata. Additionally for example, such a data packet may indicate amaximum lifetime, after which the data should be dropped. Suchinformation may also for example be programmed into applications,specified in a configuration file, etc.

Also as discussed herein, an ACK packet may be communicated from animmediate recipient of the data and also from the final destinationrecipient of the data. In a scenario in which an ACK packet or otherinformation indicates to the node that the data has been received at thedestination (or at a node that is reliable enough to consider suchdelivery to be final), the node may cease attempts to communicate thedata and remove the data from memory. An example of such operation isshown at block 1375, at which an incoming ACK directs execution flow ofthe example method 1300 to block 1380 at which the data is cleared fromstorage. This may, for example, be particularly useful in a scenario inwhich at block 1350 the data was propagated to other Mobile APs, eachindependently attempting to communicate the data to the destination. Insuch a scenario, the ACK may be propagated by the network infrastructurebut may also be propagated by the Mobile APs to each other.

Note that the example method 1300 is merely presented to illustratevarious aspects of the present disclosure and is non-limiting. Forexample, additional functionality may be performed, for example asdiscussed throughout this disclosure. Also for example, any of thefunctionality of the example method 1300 may be removed. For example,utilization of Wi-Fi hotspots may be optional, propagation of data toother Mobile APs may be immediate and non-discretionary, forhigh-priority data utilizing the cellular network may be immediate, etc.Further for example, any of the functionality may be repeated. Forexample, the number of Mobile APs to which data is propagated may beincreased after a particular amount of time has passed. Accordingly, thescope of this disclosure should not be limited by particularcharacteristics of the example method 1300 or by any example discussedherein.

As discussed with reference to block 1350, data may be communicated toother Mobile APs (or other nodes), which may then also attempt tocommunicate the data. An example method for the operation of such othernodes is provided at FIG. 14, which shows a block diagram of a method1400 in a node for delay tolerant networking, in accordance with variousaspects of the present disclosure. The example method 1400 and systemmay, for example, share any or all characteristics with the otherexample methods, networks and/or network components 100, 200, 300, 400,500-570, 600, 700, 800, 900, 1000, 1100, 1200, 1300, and 1500, discussedherein. The example method 1400 or any portion thereof may, for example,be implemented in any network node discussed herein (e.g., a Mobile APor OBU, etc.). The example method 1400 may also incorporate any or allof the functionality discussed herein.

The example method 1400 may begin executing at block 1405. At block1410, data to be propagated upstream to the Cloud (e.g., to anapplication running on a computer or server in the Cloud) is received(e.g., from another Mobile AP, etc.). The received data is stored atblock 1420.

The example method 1400 may, at block 1450, propagate the data to otherMobile APs, for example to increase the odds that some carrier of thedata will encounter a network (e.g., a Wi-Fi hotspot and/or a vehiclenetwork Fixed AP) over which the data can be communicated. Block 1450may comprise performing such propagation in any of a variety of manners.For example, block 1450 may comprise determining how many Mobile APsand/or determining which APs to send the data. There may, for example,be a target (or maximum) number of Mobile APs based on hop count. Forexample, in a scenario in which a Mobile AP was a single-hop recipientof the data, the Mobile AP may communicate the data to N (e.g., 3 or 4,etc.) other Mobile APs. Also for example, in a scenario in which aMobile AP was a second-hop recipient of the data (e.g., receiving thedata from another Mobile AP), the Mobile AP may communicate the data toM (e.g., 1 or 2) other Mobile APs. Additionally for example, in ascenario in which a Mobile AP was a third-hop recipient of the data, theMobile AP might determine that it is not allowed by the propagationprotocol to further propagate the data.

Until the time threshold T₃ is exceeded (e.g., as discussed with regardto FIG. 13) and if the data has not yet been successfully communicated,then the method 1400 may, at block 1460, comprise continuing to attemptto utilize a Wi-Fi hotspot or the vehicle network to communicate thedata, whichever is available first. Note that in this case, a pluralityof other Mobile APs may be similarly attempting to communicate the samedata to the same ultimate destination. For example, if any of the MobileAPs detects a Wi-Fi hotspot through which the Mobile AP may communicatethe data to its destination, then the Mobile AP will attempt tocommunicate the data in such manner. Also for example, if any of theMobile APs detects a Fixed AP of the vehicle network, then the Mobile APwill attempt to communicate the data in such manner.

If the time threshold T₃ is exceeded, then the method 1400 may, at block1480, comprise clearing (or removing) the data from memory. For example,block 1480 may comprise de-allocating memory that previously stored thedata and/or removing a reference to the data from a list of data tocommunicate. In this example scenario, the node implementing the method1400 may rely on the original node to utilize the cellular network orsome other failover communication method to communicate the data, if thedata warrants such treatment.

Also as discussed herein, an ACK packet may be communicated from animmediate recipient of the data and also from the final destinationrecipient of the data. In a scenario in which an ACK packet or otherinformation indicates to the node that the data has been received at thedestination (or at a node that is reliable enough to consider suchdelivery to be final), the node may cease attempting to communicate thedata and remove the data from memory. An example of such operation isshown at block 1475, at which an incoming ACK directs execution flow ofthe example method 1400 to block 1480 at which the data is cleared fromstorage. This may, for example, be particularly useful in a scenario inwhich at block 1450 the data was propagated to a plurality of MobileAPs, each independently attempting to communicate the data to thedestination.

Various system diagrams have been presented herein to provide an arrayof context examples into which systems and methods in accordance withvarious aspects of this disclosure may be integrated. Another examplecontext is provided at FIG. 15, which shows a block diagram of variouscomponents of an example mobile communication network 1500, inaccordance with various aspects of the present disclosure.

FIG. 15 shows a block diagram of various components of an examplecommunication network 1500 (e.g., a network of moving things) forproviding delay tolerant networking (DTN), in accordance with variousaspects of the present disclosure. The example system 1500 may, forexample, share any or all characteristics with the other examplemethods, networks and/or network components 100, 200, 300, 400, 500-570,600, 700, 800, 900, 1000, 1100, 1200, 1300, and 1400, discussed herein.For example, any or all of the components of the example network 1500may perform any or all of the method steps presented herein.

The example network 1500 comprises a Cloud 1530, which in turn maycomprise any of a variety of servers and/or nodes executingapplications. An example Cloud-based Application 1535 is shown. In anexample implementation, the Application(s) 1535 may operate at a sourceand/or destination for data as discussed herein. For example, one ormore memory devices of a Cloud computer or server may, for example,comprise a non-transitory computer-readable medium that comprisessoftware instructions that when executed by one or more processors,cause the Cloud computer or server to perform any or all of thefunctionality discussed herein.

The example network 1500 also comprises a Mobile AP 1510, a secondMobile AP 1520, and a Fixed AP 1525. The example network 1500 furthercomprises one or more data sources 1540 (e.g., sensors, user clientdevices, etc.).

The example Mobile AP 1510 comprises a Mobile (e.g., Vehicle) NetworkCommunication Interface (I/F) Module 1511 that is operable tocommunicate with a communication network (e.g., infrastructurecomponents, Cloud components, Fixed APs, etc.). The Mobile Network CommI/F Module 1511 may, for example, operate to communicate in accordancewith any of a variety of communication protocols (e.g., 802.11p,cellular, etc.). In an example scenario, the Mobile AP 1510 utilizes theMobile Network Comm I/F Module 1511 to communicate with a server in theCloud 1530 that is operating in accordance with the Cloud-basedApplication(s) 1535. The Mobile Network Comm I/F Module 1511 may, forexample, communicate with such server via a Fixed AP 1525 and/or any ofa variety of intermediate nodes. For example, any of the examplecommunications discussed herein between a Mobile AP and a Fixed AP,network infrastructure node, cloud component, etc., may be performedutilizing the Mobile Network Comm I/F Module 1511.

The example Mobile AP 1510 comprises a Peer-to-Peer (P2P) CommunicationInterface (I/F) Module 1511 that is operable to communicate with peernodes (e.g., Mobile APs, etc.). The P2P Comm I/F Module 1512 may, forexample, operate to communicate in accordance with any of a variety ofcommunication protocols (e.g., 802.11p, cellular, Wi-Fi, etc.). In anexample scenario, the Mobile AP 1510 utilizes the P2P Comm I/F Module1512 to communicate with one or more other Mobile APs (and/or Fixed APs)in the network 1500. The P2P Comm I/F Module 1512 may, for example,communicate with a peer node 1520 directly, via an intermediate Fixed AP1525, via any one or more of a variety of intermediate nodes, etc. Forexample, any of the example communication discussed herein between aMobile AP and another Mobile AP, etc., may be performed utilizing theP2P Comm I/F Module 1512.

The example Mobile AP 1510 comprises a Data Source CommunicationInterface (I/F) Module 1513 that is operable to communicate with datasources (e.g., sensor systems, general data sources, user clientdevices, etc.). The Data Source Comm I/F Module 1513 may, for example,operate to communicate in accordance with any of a variety ofcommunication protocols (e.g., Wi-Fi, Bluetooth, UWB, cellular, wiredinterface, etc.). In an example scenario, the Mobile AP 1510 utilizesthe Data Source Comm I/F Module 1513 to communicate with one or moreother data sources (e.g., sensors, general data sources, etc.) in thenetwork 1500. The Data Source Comm I/F Module 1513 may, for example,communicate with a sensor directly, via any one or more of a variety ofintermediate nodes, etc. For example, any of the example communicationdiscussed herein between a Mobile AP and a data source, etc., may beperformed utilizing the Data Source Comm I/F Module 1513.

The example Mobile AP 1510 comprises a Cellular Network CommunicationInterface Module 1514 that is operable to communicate with one or morecellular networks (e.g., via a cellular base station 1550, etc.). TheCellular Network Comm I/F Module 1514 may, for example, operate tocommunicate in accordance with any of a variety of cellularcommunication protocols (e.g., LTE, 3G protocols, etc.). For example,any of the example cellular communication discussed herein between aMobile AP and the cellular network may be performed utilizing theCellular Network Comm I/F Module 1514.

The example Mobile AP 1510 comprises a Hot Spot Communication InterfaceModule 1515 that is operable to communicate with one or more hot spots1555 (e.g., public and/or private Wi-Fi hot spots, etc.). The Hot SpotComm I/F Module 1515 may, for example, operate to communicate inaccordance with any of a variety of hot spot protocols (e.g., Wi-Fi,etc.). For example, any of the example hot spot communication discussedherein between a Mobile AP and a hot spot may be performed utilizing theHot Spot Comm I/F Module 1515.

The example Mobile AP 1510 comprises various modules 1515 that areoperable to perform (or manage) any or all of the functionalitydiscussed herein. Such modules 1515 may, for example, share any or allcharacteristics with the modules shown in the example system 800 of FIG.8. Such modules 1515 may, for example, operate to perform any or all ofthe DTN-related functionality discussed herein (e.g., utilizing thevarious communication interface modules 1511, 1512, 1513, and 1514. Forexample, the modules 1515 may comprise an API module that operates toperform any or all of the API functionality discussed herein. Also forexample, the modules 1515 may comprise a Receive module that operates toperform any or all of the data receiving functionality discussed herein(e.g., utilizing any or all of the communication interface modules 1511,1512, 1513, and 1514). Additionally for example, the modules 1515 maycomprise a Storage module that operates to perform any or all of thedata storage functionality discussed herein (e.g., utilizing the MemoryDevice(s) 1519). Further for example, the modules 1515 may comprise aRouting module that operates to perform any or all of the data routing(or communicating) functionality discussed herein (e.g., utilizing anyor all of the communication interface modules 1511, 1512, 1513, and1514). Still further for example, the modules 1515 may comprise aNeighboring module that operates to perform any or all of thefunctionality discussed herein with regard to maintaining an accuratelist of neighboring nodes of a node.

The example Mobile AP 1510 may also comprise one or more Applications1517. Such Applications may, for example, request and/or utilize and/orprovide data, the communication of which is managed by the variousmodules 1515. In an example scenario, an Application 1517 may comprisean on-board application of the Mobile AP 1510 that operates to requestand/or receive collected data from external data sources (e.g., sensors,user client devices, etc.). Such Application 1517 may, for example,communicate with a counterpart (or central) application in the Cloud1530.

The example Mobile AP 1510 may also comprise one or more Processors 1518and Memory Devices 1519. The Processor(s) 1518 may, for example,comprise any of a variety of processor characteristics. For example, theProcessor(s) 1518 may comprise one or more of a general purposesprocessor, RIS processor, microcontroller, ASIC, DSP, video processor,etc.). The Memory Device(s) 1519 may, for example comprise any of avariety of memory characteristics. For example, the Memory Device(s)1519 may comprise a volatile memory, non-volatile memory, etc. TheMemory Device(s) 1519 may, for example, comprise a non-transitorycomputer-readable medium that comprises software instructions that whenexecuted by the Processor(s) 1518, cause the Mobile AP 1210 to performany or all of the functionality discussed herein (e.g., with regard tothe example methods discussed herein, etc.). The Memory Device(s) 1519may, for example, be utilized by a Storage module of the various modules1515 for storing data.

Note that the second Mobile AP 1520, the Fixed AP 1525, and/or any of avariety of network nodes may comprise configurations that share any orall aspects with the example Mobile AP 1510.

In general, the systems and methods presented herein provide a varietyof benefits. For example, cost to transport data to and/or from thecloud is reduced. The reliance on and/or utilization of cellular networkbandwidth is reduced. Flexibility is provided regarding data deliveryrequirements, providing for low cost communication when allowed. Free orlow-cost communication pathways are leveraged to the extent possible.Delay tolerant networking is provided with the capability to utilize thecellular network as a fault-back mechanism for data that must becommunicated reliably. Also, communication resources may be directedtoward immediate communication needs and away from communication thatcan be delayed.

In an example implementation of a vehicle communication network, aconsiderable amount of non real-time data may need to be collectedand/or disseminated. Acceptable delivery times for such data to thedestination may range from minutes, to hours, etc. Such data may, forexample, comprise sensor data, advertisement information, multimediainformation, etc. A communication network implemented in accordance withvarious aspects of this disclosure provides for such operation in anefficient manner, for example with regard to cost, bandwidthutilization, etc.

In general, the systems and methods presented herein, in accordance withvarious aspects of the present disclosure, adapt the rules (or strategyor plan) by which data is gathered. Such adaptability may, for example,be performed in a distributed fashion. For example, the determiningplans for collecting data as well as the actual collection of the datamay be performed in a distributed manner. In an example implementation,a combination of central control and distributed control of datacollection activities may be utilized. In an example implementation,control of data collection activities may be generally completelydistributed among the data collecting nodes themselves with a minimalamount of central oversight.

The manner in which data is collected may thus be optimized based on anyor a large number of considerations, for example regarding environment,network operation, overall context, individual node contexts, etc. Anyor all nodes of the system may provide information relevant to thecollection of data by the network nodes.

In a network implementation in accordance with various aspects of thepresent disclosure, a network of moving things may be utilized as aflexible and efficient backbone for sensor data communication. Such anetwork may provide the needs of any of a variety of organizations, forexample business enterprises, municipalities, infrastructure maintenanceorganizations, security organizations, etc.

In an example implementation, mobile-to-mobile communication links maybe utilized to share control information between nodes, to sharecollected data between nodes, to share storage, processing, and/orcommunication responsibilities for such collected data, etc.

Though this disclosure generally discussed the collection of data fromdata sources, it should be readily understood that the scope of thisdisclosure also applies to the communication of information to the datasources. For example, any or all of the network components discussedherein may be utilized to share collected data between data sources, tocommunicate other data (e.g., control or configuration information,program update information, etc.) to the data sources (e.g., sensorsystems, etc.), etc. Such reverse communication may also be incorporatedinto any or all aspects of the data collection (or communication)planning discussed herein.

In accordance with various aspects of this disclosure, examples of thenetworks and/or components thereof presented herein are provided in U.S.Provisional Application Ser. No. 62/222,192, titled “CommunicationNetwork of Moving Things,” filed on Sep. 22, 2015, which is herebyincorporated herein by reference in its entirety.

In accordance with various aspects of this disclosure, the networksand/or components thereof presented herein are provided with systems andmethods for integrating such networks and/or components with othernetworks and systems, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/221,997, titled “IntegratedCommunication Network for A Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for synchronizing such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,016, titled “Systems and Methods forSynchronizing a Network of Moving Things,” filed on Sep. 22, 2015, whichis hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,042, titled “Systems and Methods forManaging a Network of Moving Things,” filed on Sep. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for monitoring such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,066, titled “Systems and Methods forMonitoring a Network of Moving Things,” filed on Sep. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for detecting and/or classifying anomalies insuch networks and/or components, non-limiting examples of which areprovided in U.S. Provisional Application Ser. No. 62/222,077, titled“Systems and Methods for Detecting and Classifying Anomalies in aNetwork of Moving Things,” filed on Sep. 22, 2015, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing mobility in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,098, titled “Systems and Methodsfor Managing Mobility in a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing connectivity in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,121, titled “Systems and Methodsfor Managing Connectivity a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for collecting sensor data in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,135, titled “Systems and Methodsfor Collecting Sensor Data in a Network of Moving Things,” filed on Sep.22, 2015, which is hereby incorporated herein by reference in itsentirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for interfacing with such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,145, titled “Systems and Methodsfor Interfacing with a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for interfacing with a user of such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,150, titled “Systems and Methodsfor Interfacing with a User of a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for data storage and processing in such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,168, titled “Systems and Methodsfor Data Storage and Processing for a Network of Moving Things,” filedon Sep. 22, 2015, which is hereby incorporated herein by reference inits entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for vehicle traffic management in such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,183, titled “Systems and Methodsfor Vehicle Traffic Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for environmental management in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,186, titled “Systems and Methodsfor Environmental Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing port or shipping operation in suchnetworks and/or components, non-limiting examples of which are providedin U.S. Provisional Application Ser. No. 62/222,190, titled “Systems andMethods for Port Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing the accuracy of positioning orlocation information based at least in part on historical data,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/244,828, titled “Utilizing Historical Data toCorrect GPS Data in a Network of Moving Things,” filed on Oct. 22, 2015,which is hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing the accuracy of position or locationof positioning or location information based at least in part on theutilization of anchors, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/244,930, titled “Using Anchorsto Correct GPS Data in a Network of Moving Things,” filed on Oct. 22,2015, which is hereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing communication between applications,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/246,368, titled “Systems and Methods forInter-Application Communication in a Network of Moving Things,” filed onOct. 26, 2015, which is hereby incorporated herein by reference in itsentirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for probing, analyzing and/or validatingcommunication, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/246,372, titled “Systems and Methodsfor Probing and Validating Communication in a Network of Moving Things,”filed on Oct. 26, 2015, which is hereby incorporated herein by referencein its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for adapting communication rate, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/250,544, titled “Adaptive Rate Control for Vehicular Networks,” filedon Nov. 4, 2015, which is hereby incorporated herein by reference in itsentirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for reconfiguring and adapting hardware,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/273,878, titled “Systems and Methods forReconfiguring and Adapting Hardware in a Network of Moving Things,”filed on Dec. 31, 2015, which is hereby incorporated herein by referencein its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for optimizing the gathering of data, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/253,249, titled “Systems and Methods for Optimizing Data Gathering ina Network of Moving Things,” filed on Nov. 10, 2015, which is herebyincorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing delay tolerant networking,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/257,421, titled “Systems and Methods for DelayTolerant Networking in a Network of Moving Things,” filed on Nov. 19,2015, which is hereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for improving the coverage and throughput ofmobile access points, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/265,267, titled “Systems andMethods for Improving Coverage and Throughput of Mobile Access Points ina Network of Moving Things,” filed on Dec. 9, 2015, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for coordinating channel utilization, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/270,858, titled “Channel Coordination in a Network of Moving Things,”filed on Dec. 22, 2015, which is hereby incorporated herein by referencein its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for implementing a network coded mesh network in thenetwork of moving things, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/257,854, titled “Systems andMethods for Network Coded Mesh Networking in a Network of MovingThings,” filed on Nov. 20, 2015, which is hereby incorporated herein byreference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for improving the coverage of fixed access points,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/260,749, titled “Systems and Methods forImproving Fixed Access Point Coverage in a Network of Moving Things,”filed on Nov. 30, 2015, which is hereby incorporated herein by referencein its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing mobility controllers and their networkinteractions, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/273,715, titled “Systems and Methodsfor Managing Mobility Controllers and Their Network Interactions in aNetwork of Moving Things,” filed on Dec. 31, 2015, which is herebyincorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for managing and/or triggering handovers ofmobile access points, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/281,432, titled “Systems andMethods for Managing and Triggering Handovers of Mobile Access Points ina Network of Moving Things,” filed on Jan. 21, 2016, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing captive portal-related control andmanagement, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/268,188, titled “CaptivePortal-related Control and Management in a Network of Moving Things,”filed on Dec. 16, 2015, which is hereby incorporated herein by referencein its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for extrapolating high-value data, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/270,678, titled “Systems and Methods to Extrapolate High-Value Datafrom a Network of Moving Things,” filed on Dec. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing remote software updating anddistribution, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/272,750, titled “Systems and Methodsfor Remote Software Update and Distribution in a Network of MovingThings,” filed on Dec. 30, 2015, which is hereby incorporated herein byreference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing remote configuration updating anddistribution, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/278,662, titled “Systems and Methodsfor Remote Configuration Update and Distribution in a Network of MovingThings,” filed on Jan. 14, 2016, which is hereby incorporated herein byreference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for adapting the network, for exampleautomatically, based on user feedback, non-limiting examples of whichare provided in U.S. Provisional Application Ser. No. 62/286,243, titled“Systems and Methods for Adapting a Network of Moving Things Based onUser Feedback,” filed on Jan. 22, 2016, which is hereby incorporatedherein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing and/or guaranteeing data integritywhen building or performing data analytics, non-limiting examples ofwhich are provided in U.S. Provisional Application Ser. No. 62/278,764,titled “Systems and Methods to Guarantee Data Integrity When BuildingData Analytics in a Network of Moving Things,” Jan. 14, 2016, which ishereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing self-initialization and/or automatedbootstrapping of mobile access points, non-limiting examples of whichare provided in U.S. Provisional Application Ser. No. 62/286,515, titled“Systems and Methods for Self-Initialization and Automated Bootstrappingof Mobile Access Points in a Network of Moving Things,” filed on Jan.25, 2016, which is hereby incorporated herein by reference in itsentirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing power supply and/or utilization,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/295,602, titled “Systems and Methods for PowerManagement in a Network of Moving Things,” filed on Feb. 16, 2016, whichis hereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for automating and easing the installation and setupof the infrastructure, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/299,269, titled “Systems andMethods for Automating and Easing the Installation and Setup of theInfrastructure Supporting a Network of Moving Things,” filed on Feb. 24,2016, which is hereby incorporated herein by reference in its entirety.

In summary, various aspects of this disclosure provide systems andmethods for optimizing data communication in a network of moving things.As non-limiting examples, various aspects of this disclosure providesystems and methods for communicating delay tolerant information in anetwork of moving things, for example comprising any of a variety oftypes of vehicles (e.g., autonomous vehicles, vehicles controlled bylocal operators, vehicles controlled by remote operators, etc.). Whilethe foregoing has been described with reference to certain aspects andexamples, it will be understood by those skilled in the art that variouschanges may be made and equivalents may be substituted without departingfrom the scope of the disclosure. In addition, many modifications may bemade to adapt a particular situation or material to the teachings of thedisclosure without departing from its scope. Therefore, it is intendedthat the disclosure not be limited to the particular example(s)disclosed, but that the disclosure will include all examples fallingwithin the scope of the appended claims.

What is claimed is:
 1. A communication network mobile access point (MAP)comprising: at least one module operable to, at least: provide wirelesscommunication services to client devices as the MAP is moving; receive adata packet; during a first time period, first attempt to communicatethe data packet to a destination through at least a first type ofcommunication network access point, wherein the at least a first type ofcommunication network access point does not comprise another MAP; andduring a second time period after the first time period, second attemptto communicate the data packet to the destination through at least asecond type of communication network access point, wherein the secondtype of communication network access point comprises one or more otherMAPs, wherein the at least one module is operable to select a MAP of theone or more other MAPs based, at least in part, on a predicted futurelocation.
 2. The mobile access point (MAP) of claim 1, wherein the atleast one module is operable to determine a quantity of the one or moreother MAPs.
 3. The mobile access point (MAP) of claim 2, wherein the atleast one module is operable to determine the quantity of the one ormore other MAPs based, at least in part, on hop count.
 4. The mobileaccess point (MAP) of claim 2, wherein the at least one module isoperable to determine the quantity of the one or more other MAPs based,at least in part, on time.
 5. The mobile access point (MAP) of claim 4,wherein the at least one module is operable to determine the quantity ofthe one or more other MAPs based, at least in part, on a particularamount of time that has passed.
 6. The mobile access point (MAP) ofclaim 1, wherein the at least one module is operable to select a MAP ofthe one or more other MAPs based, at least in part, on geographicallocation information.
 7. The mobile access point (MAP) of claim 6,wherein the geographical location information comprises a geographicallocation information of the selected MAP.
 8. The mobile access point(MAP) of claim 1, wherein the at least one module is operable to selecta MAP of the one or more other MAPs based, at least in part, on a knowntrajectory.
 9. The mobile access point (MAP) of claim 8, wherein theknown trajectory comprises a known trajectory of the selected MAP. 10.The mobile access point (MAP) of claim 9, wherein the at least onemodule is operable to select a MAP of the one or more other MAPs basedalso, at least in part, on a trajectory of the MAP.
 11. The mobileaccess point (MAP) of claim 1, wherein the predicted future location isa predicted future location of the selected MAP.
 12. The mobile accesspoint (MAP) of claim 11, wherein the at least one module is operable toselect the MAP of the one or more other MAPs based, at least in part, onthe predicted future location of the selected MAP being in a coveragearea of another access point.
 13. The mobile access point (MAP) of claim12, wherein the another access point is a fixed access point (FAP) of avehicle communication network.
 14. The mobile access point (MAP) ofclaim 1, wherein the first time period and the second time period aredetermined prior to the time at which the data packet is received.
 15. Acommunication network mobile access point (MAP) comprising: at least onemodule operable to, at least: provide wireless communication services toclient devices as the MAP is moving; receive a data packet from a sourceMAP; and during a first time period, at least: first attempt tocommunicate the data packet to a destination through at least a firsttype of communication network access point, wherein the at least a firsttype of communication network access point does not comprises anotherMAP; and while first attempting to communicate the data packet to thedestination through the at least a first type of communication networkaccess point, also attempt to communicate the data packet to thedestination through one or more other MAPs, wherein the at least onemodule is operable to select a MAP of the one or more other MAPs based,at least in part, on a predicted future location of the selected MAP.16. The mobile access point (MAP) of claim 15, wherein the at least onemodule is operable to determine a quantity of the one or more otherMAPs.
 17. The mobile access point (MAP) of claim 15, wherein the atleast one module is operable to select a MAP of the one or more otherMAPs based, at least in part, on geographical location information ofthe selected MAP.
 18. The mobile access point (MAP) of claim 15, whereinthe at least one module is operable to select a MAP of the one or moreother MAPs based, at least in part, on a known trajectory of theselected MAP.
 19. The mobile access point (MAP) of claim 18, wherein theat least one module is operable to select a MAP of the one or more otherMAPs based also, at least in part, on a known trajectory of the MAP. 20.A communication network mobile access point (MAP) comprising: at leastone module operable to, at least: receive a data packet from a sourceMAP; and during a first time period, at least: first attempt tocommunicate the data packet to a destination through at least a firsttype of communication network access point, wherein the at least a firsttype of communication network access point does not comprises anotherMAP; and while first attempting to communicate the data packet to thedestination through the at least a first type of communication networkaccess point, also attempt to communicate the data packet to thedestination through one or more other MAPs, wherein the at least onemodule is operable to cease attempting to communicate the data packet tothe destination while the source MAP continues to attempt to communicatethe data packet to the destination.
 21. A communication network mobileaccess point (MAP) comprising: at least one module operable to, atleast: provide wireless communication services to client devices as theMAP is moving; receive a data packet; during a first time period, firstattempt to communicate the data packet to a destination through at leasta first type of communication network access point, wherein the at leasta first type of communication network access point does not compriseanother MAP; and during a second time period after the first timeperiod, second attempt to communicate the data packet to the destinationthrough at least a second type of communication network access point,wherein the second type of communication network access point comprisesone or more other MAPs, wherein the first time period and the secondtime period are determined prior to the time at which the data packet isreceived.